Twitxy Saved

UptimeRobot

Verified account This account is verified. Learn more

@uptimerobot

The world's leading uptime monitoring service.
Get 50 monitors totally FREE! ๐Ÿ’š
uptimerobot.com Joined January 2010
49 Following 17K Followers 5.3K Posts

Latest posts 5

UptimeRobot Verified account @uptimerobot
Microsoft 365 has been degraded since Thursday. Outlook couldn't open mailboxes, Teams couldn't schedule meetings, and Copilot Chat failed to load.

Our check on outlook.com started failing at 18:24 UTC on Thursday. By Friday morning it had logged 33 separate incidents: timeouts, 503s and 400s, with Outlook coming back in between and then dropping again. Microsoft described the same thing from the inside, with restarted servers going unresponsive again once traffic returned.

Other tools ran into trouble because of it. Zendesk's Exchange connector, Twilio's email delivery to Microsoft inboxes and Anthropic's Microsoft 365 connector all posted incidents of their own.

We put together the timeline, what Microsoft said, and what our monitors saw. Link in the first comment.

#Microsoft365 #DevOps
UptimeRobot Verified account @uptimerobot
You can post the first outage update before you know the cause. Say what's affected and when the next update comes.

Copy-paste templates for every stage of an incident:

uptimerobot.com/knowledge-hub/โ€ฆ
uptimerobot.com System Outage Notification Templates: Copy-paste Samples Need system outage notification samples for every incident stage? Get short templates, channel variations, and a full outage timeline
UptimeRobot Verified account @uptimerobot
In 286.9M downtime notifications over a year, Friday had fewer incidents than Monday. Tuesday had the most.

Looks like teams stopped shipping risky changes on Fridays and moved them to Tuesday.

uptimerobot.com/knowledge-hub/โ€ฆ
uptimerobot.com The State of Downtime: What 286M+ Incidents Reveal | UptimeRobot Most outages feel random when they happen, but when you zoom out far enough, downtime starts looking a lot less chaotic.