Anybody else experiencing severe issues with the Spiceworks Community Platform after last nights maintenance window ?

The Spiceworks tools seem to be working again and don’t run into timeouts or other symptoms.

But whatever I do or navigate in Spiceworks Community Platform, I guess that at least 80% of actions result in

504 Gateway Time-Out

or

502 Bad Gateway

or

Failed to load subscription data.

Using a reload of web page in the web browser usually works. So the error has to do with data on the Spiceworks back-end needing too much time to get delivered to Spiceworks web server and its cache. A reload seems to work as it seems that the data gets delivered after the web server lost hope to get the data and a reload may find it on some cache.

It doesn’t matter which action I take. Starting a new tab with subscribed view, clicking on a topic, clicking on feature requests category, …

These symptoms happened before too, but much less frequently. In the past, this happened perhaps once every one or three weeks with perhaps 100+ clicks per day. Now it happens more often than 4 out of 5 clicks.

And would be nice if tagging Community Support team becomes possible again ! I needed perhaps 8+ trials before getting any community tag offered over a period of more than 10 minutes !

I was complaining about such symptoms in the past repeatedly. After several complaints, I finally got a feedback that such symptoms are known and get monitored. But I did not get any details what gets monitored. Reminds me of some security teams claiming the same on security incidents I reported. Their response allowed to conclude that either they don’t know how to do their job or that they were not monitoring. In case of Spiceworks, I don’t fear that they don’t know how to do their job. But my fear is either they are not monitoring what they indicate or having a system architecture mismatch and misuse.

@community-team

5 Spice ups

Maintenance appears to be ongoing. There must have been a hiccup or two.

1 Spice up

Yeah, everything is slow as a week in jail at the moment

You mean this? Nothing as impressive as a cloud-based company that can’t keep it’s cloud up.

1 Spice up

Something is up and something is slow. And I’m not sure to which extend that company has already migrated to Cloud or is using some mix of Cloud and web services with insufficient control and insufficient monitoring of dependencies. To me it sounds that the company claims more Cloud than already migrated.

No, I don’t mean this. Your screenshot is of 23:25 UTC and the announcement and reality is that community will not be available since 23:00 UTC.

Yup, had this too. I couldn’t see profile pictures for quite some time either, but seem to be re-appearing now.

1 Spice up

What you call pictures, I call avatars. I could always see avatars, but not always those of those Spiceheads, including my own. Some random replies in topics displayed with the correct avatars of those Spiceheads, and some other random avatars displayed with the standard gray avatar without initials which is normally used when no avatar was ever configured.

For those not aware of some further actions and discussion, here is a reference what Spiceworks was doing and needed to do after end of extended maintenance window in order to return to expected behavior several hours later. As I was requested , I reported further details there . That includes this aspect with avatars as well as an additional error web page.