39

Worldbuilding and Biology, for example, have been offline for about 15 minutes, Science Fiction & Fantasy and Psychology & Neuroscience for somewhat less. Meta disappeared for a bit, but it is back now.

Do we have an update?

I'm in the UK, south of London if relevant.

Update: Worldbuilding has now gone from the "We are offline.." page to "Service unavailable" as of 5 minutes after posting this. Ditto the rest on checking.

7
  • 23
    There was a very active DDoS attack today, we are still in the process of mitigating it. More details to come Monday.
    – Josh Zhang StaffMod
    Feb 7 at 5:20
  • 19
    @JoshZhang you probably hear this often but what's the point in having a status blog and Twitter account if they're not used effectively? Also, if you do hear that often, I'd say that's a problem in and of itself
    – Phil
    Feb 7 at 5:43
  • 14
    @Phil we're actively working on improving our processes around status updates, today all hands were very busy fighting the fire.
    – Josh Zhang StaffMod
    Feb 7 at 5:50
  • 2
    @JoshZhang what exactly was completed? Can you please explain as edit to existing answer by Tom, or a new answer? It's not clear as it says only "working on improving our processes", or "in the process of revising our outage communication process" but without details. May 2 at 14:34
  • 5
    @ShadowWizardSaysNoMoreWar we implemented a way to update StackStatus directly from our incident management tool. We used to manually log in to Twitter which was a lot of friction especially during an outage.
    – Josh Zhang StaffMod
    May 2 at 14:54
  • 3
    @JoshZhang thanks, this is better indeed, but answer says "Our plan is to roll out a new status page similar to what many other websites use; this will replace our other mechanisms" - guess it's beyond the scope of this specific bug report, so will there be official announcement when that page will be rolled out? May 3 at 5:47
  • 2
    @ShadowWizardSaysNoMoreWar we are currently evaluating the replacement status page and working through implementation steps / timeline. I'm not sure if we'll have an official announcement but will make a note to revisit when time comes.
    – Josh Zhang StaffMod
    May 3 at 18:52

1 Answer 1

21

I am a Product Manager in the Platform Engineering team.

Our apologies for the lack of communication during the previous outage. As you correctly pointed out, we were suffering an outage and our usual channels were not used to communicate status. You are also correct in that our communication during outages has been (to be polite) uneven lately.

We apologize and are working to do better in the future.

We are currently in the process of revising our outage communication process to make it more streamlined and consistent. Our plan is to roll out a new status page similar to what many other websites use; this will replace our other mechanisms.

As of May 2022, we implemented a way to update StackStatus directly from our incident management tool. We used to manually log in to Twitter which was a lot of friction especially during an outage, so this should improve the overall process.

7
  • 9
    "Our plan is to roll out a status page" - Isn't that what this is? "revising our outage communication" - Just make sure someone has the keys to the Twitter account.
    – MrWhite
    Feb 8 at 0:43
  • 2
    Thanks, but any details about the attack itself? Was it blocked? Did you take any measures to block such attack in the future? Feb 8 at 6:50
  • 4
    @MrWhite Not really. That domain currently points to a Tumblr where things can be posted like any other social media. This is a better example of a status page.
    – animuson StaffMod
    Feb 8 at 6:59
  • 2
    Yeah, I hope it's better than the purported better Facebook example. Three clicks deep to get details and your get blown off with boilerplate: status.fb.com/adsmanager/history - could have guessed those three very similar reports without looking. Really better: ClickUp - Dashboard, Asana - Kaban Board, or a dedicated UpTime monitor.
    – Rob
    Feb 8 at 16:29
  • 2
    @MrWhite Thank you for pointing that out. I've added the word "new" to that sentence to clarify for others that may have been similarly confused.
    – Tom Limoncelli StaffMod
    Feb 8 at 23:01
  • "We apologize and are working to do better in the future." Is there a timeline on this? During the latest attack, in the Tavern, Catija claimed it wasn't a DDoS. Turns out it was. Now, we all make mistakes and you won't have a new system set-up in a week naturally, but the current communication is significantly worse than we had years ago (pre-2019).
    – Mast
    Mar 15 at 6:51
  • 1
    @Mast I guess it's kind of mixed causes and Catija only reported the latter. The DDoS attack itself was mitigated earlier (possibly within the first 2 hours), but the side-effect took the server down longer than the attack (more than 10 hours) Mar 15 at 7:50

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .