Shows that all these availability zones and regions don't really help if an outage can knock out a whole cloud provider. And that's not specific to Microsoft. The only way to really ensure uptime is to use two providers. Sadly, that's basically only possible with on-prem/colocation where traffic is cheap.
Not sure if it's directly related, but GitHub is also experiencing issues: <a href="https://www.githubstatus.com/" rel="nofollow">https://www.githubstatus.com/</a>
At work, we all got kicked out of a teams meeting an hour back and sending/receiving e-mails on Outlook seems to be slow.<p>Location: Chennai, India
Every Azure product I've had to use has been lousy in every possible way. Azure DevOps at my last employer was a nightmare and nobody in the company liked it, not even the managers who decided on it.
I have some Azure services that are not able to consistently make outbound HTTP requests to my heartbeat monitoring service so I'm getting alert after alert this morning. This is just the nudge I needed, and I'll be moving the whole thing to Linode later this afternoon.
Wouldn't it be quite simple to set up an unofficial status page that just pings some relevant services and if they have a disastrous outage at least, it shows it?<p>Because I think it's clear that their status page is useless and "manual".
> We've identified a potential networking issue and are reviewing telemetry to determine the next troubleshooting steps. You can find additional information on our status page at <a href="https://msft.it/6011eAYPc" rel="nofollow">https://msft.it/6011eAYPc</a> or on SHD under MO502273.
<a href="https://downdetector.dk/" rel="nofollow">https://downdetector.dk/</a> indicates several MS products and services are having problems. Here is the status from MS on Twitter: <a href="https://twitter.com/MSFT365Status/status/1618149579341369345" rel="nofollow">https://twitter.com/MSFT365Status/status/1618149579341369345</a>
Edit: Added this link which apparently is the new status page and seems to be updated: <a href="https://status.office365.com/" rel="nofollow">https://status.office365.com/</a>
Auth via Microsoft ID is degraded, our platform is blipping (cache retries, message retries due to packet loss), access to the Azure portal is degraded and the Azure status page isn't loading consistently.
<i>> The issue is causing impact in waves, peaking approximately every 30 minutes.</i><p>Does anyone have any general ideas on what kind of outage manifests itself like this? Devices retrying to authenticate every 30 minutes and finding the service is down perhaps?
Many games that use Azure PlayFab are down as well due to this. Both PlayFab services and PlayFab MPS game-server hosting are currently broken.<p><a href="https://status.playfab.com/" rel="nofollow">https://status.playfab.com/</a>
ThousandEyes public outage map shows the scale of the Office365 outage: <a href="https://www.thousandeyes.com/outages/" rel="nofollow">https://www.thousandeyes.com/outages/</a>
Cloud is the new power grid. When it goes down, we lose power to everything. Will we learn from the grid and decentralise some of the compute and cloud services?
Anyone else remember the bad Windows Defender virus signature they put out on Friday the 13th a couple weeks ago? Microsoft is not having a good start to their year.
What's the point of having a status page if it doesn't indicate the issues?
<a href="https://status.azure.com/en-us/status" rel="nofollow">https://status.azure.com/en-us/status</a><p>Azure, Teams, Outlook are almost down from Greece and Germany, and their status page shows that everything is fine :-)
Azure is the most developer hostile cloud environment. I have zero sympathy for people being affected by this because if you voluntarily use Azure then this is what you deserve. Sorry for being so miserable, but Azure has given me soooo much grief over the last 10 years that I'm just completely done with this shitshow of a platform.