Ask HN: Microsoft/Azure Outage?
For the past 5 minutes all of our Microsoft Cloud connections are down. Anyone else? The Status page won't even load.
For the past 5 minutes all of our Microsoft Cloud connections are down. Anyone else? The Status page won't even load.
The Status page is not working well, but I managed to subscribe to their RSS feed and it has been sending out updates periodically. I'll post some of them here.
7:52 PM UTC: We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service.
7:30 PM UTC: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service.
7:16 PM UTC: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've also moved traffic for some services off the affected infrastructure to further reduce load, with additional traffic moves in progress.
6:59 PM UTC: We've completed redistributing connection traffic across our worldwide infrastructure, and we're moving additional traffic off the affected infrastructure to further reduce load. We're also restarting affected servers to return them to service. In parallel, we're investigating whether the elevated traffic reflects a genuine increase in requests or a shift in how traffic is being routed across our infrastructure.
Not really a big deal, but it is presently 8pm UTC time. I'm curious why their RSS feed seems to be 2 hours off?
you notice how good LLMs are at time?
Ah no that was a mistake on my part! RSS Feed was in EST and I misremembered the difference
They rolled back the 7:52 UTC update to the 730 one now....guess it didnt work
Isn't this the company that is trying to get rid of 25% of their employees?
Status page is down. Much of our org is halted.
Fingers crossed that Azure isn't impacted (seems fine so far)
(https://www.geekwire.com/2026/microsoft-makes-new-voluntary-...)
> Isn't this the company that is trying to get rid of 25% of their employees?
Just clarifying this in general, when a company makes a voluntary offer to some segment of employees, especially at this size, it is a statistics game of how many people accept the buy out.
They did not make the offer to 25% of the employees to downsize by 25%, they did it to downsize by 5% (or something like that), and then made the offer based on how many they expect to accept. This is specifically covered in this line of the geekwire article:
> Microsoft didn’t provide a projection for how many employees will accept, but the company told GeekWire it anticipates a much smaller share than the roughly 30% who took its earlier voluntary retirement offer, which went to longtime employees more likely to take the deal.
They probably expect 10-20% of those offered to take it, which would result in a 2.5-5% total downsizing.
Yeah - I get it. Just poking the bear a bit. We've had some major incidents this year from multiple vendors, it has been aggravating.
Hmm. More than normal?
And everybody has spent a year letting AI write code. Correlation is not causation, but I wonder...
[delayed]
Why do they offer these buy outs at all, doesn't the US have at will employment?
Or is this just a gesture of goodwill to avoid people jumping the ship on their own?
At will applies on a one by one basis - at a certain headcount, WARN legislation applies https://www.dol.gov/agencies/eta/layoffs/warn
And the other part is the "goodwill" you mention - if you jettison people for nothin en masse, word gets out, and make it hard to hire in the future
A layoff of any real size has negative impacts to their unemployment insurance premiums and restricts their ability to file PERM for employees. Meeting those targets with voluntary separation prevents those impacts.
If you lay people off, you’re on the hook for their unemployment. A voluntary buyout avoids that, and also avoids mandatory reporting for layoffs.
Voluntary reductions do not have the same reporting requirements or protections that actual layoffs have.
I think both parties probably benefit; people who are more likely to take the offer are those who have another reason to leave (unfulfilled, etc). This will benefit the company in the long run because they can eventually replace them with someone who want to join (people applying for the job).
Can go the other way though: people who've been there for a while, are motivated and back themselves to get another job will take redundancy (i.e. the people you want to keep).
People who aren't motivated and/or don't back themselves to get another job will stay (i.e. probably the people you want to get rid of)
You can at will fire but that doesnt stop lawsuits. Most of these require signing docs to get the payout. It is a way to cut cleanly and derisk the cut
The fact that it is always Big Even Number shows how stupid it is. Imagine if it was serious like "23.5176%" then you'd know they actually did their homework on leaning up operations instead of just cutting off limbs and seeing if it can still walk or not.
I can't access my Outlook.com account so I guess Azure's having problems.
The CFO said in an interview they only expected 3% or less to actually take the offer.
> Current status: We’re investigating an issue impacting multiple Microsoft 365 services and we've determined the affected infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. We're restarting and repairing impacted portions of this infrastructure to restore capacity, and reviewing an unexpected increase in a specific type of service traffic to determine whether it's contributing to the elevated load. In parallel, we're evaluating options to redirect traffic to alternate infrastructure to expedite relief.
DDOS?
Too many AI agents connecting at once?
sam altman needs a big headline to shore up AI funding
Perhaps they will attempt to "conscript" all of our RAM.
Maybe people trying to catch the next Nvidia headline ahead of everyone else, wherever it may be found in (likely someone's inbox.)
Edit: Oh, there it is.
isn't Microsoft 365 called Copilot now?
It’s actually O365 by Microsoft featuring Copilot by Bill Gates.
The Copilot O365 Gates, Bill G==B signature box
lol
At this point Microsoft would be better off using Copilot to brand itself.
Recursive self-promotion.
My guess: too many DC resources dedicated to AI, leaving insufficient free capacity to handle traffic spikes
I laughed then realized this is plausible
>reviewing an unexpected increase in a specific type of service traffic to determine whether it's contributing to the elevated load
This seems to be the smoking gnu, now what would it be ...
This seems to be the smoking gnu, now what would it be ...
I saw a frog smoking on The Little Rascals once, but never a gnu.
If Outlook can go down because of DDOS then it's a much worse problem.
Probably self inflicted by some code change, as they mention "specific type of service traffic".
EDIT: Seems like now they confirmed that: "We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service."
[delayed]
Reminds me of this https://www.reuters.com/sustainability/boards-policy-regulat...
I'm amazed to see so many services down and to see that Github and Github actions are still working
For now.
One of GitHub's services will be down again by next week.
Well, my mac CI runs aren't being picked up, and they eventually fail because of it. So maybe wherever connects the orchestrator to the machines is having issues.
I spoke too soon!
Software / software service quality has been declining for a few years IMO.
Coincidentally with massive programmer layoffs?
This usually isn't a software quality issue, it's overcomplicated infrastructure failures cascading through a complex environment causing additional systems to fall over.
AI agents should be able to resolve this quicker than employees, right?
Service quality is in better hands after the layoffs, at least that’s what investors are led to believe.
AI is good at incident diagnosis, but AI slop code may have actually caused this: designing to avoid cascading failures is something AI doesn't do so well
The place where I consistently see AI/LLMS/Agents/language-widgets-with-tools fail at making decent code (and more often configuration) is infrastructure.
The number of times it has spit out a python program where a much simpler bash script would do, is too many to count.
I have a pet theory that if you don't know what you really want, and aren't skilled enough to understand what you got, infra code is THE WORST.
Anecdote: I wanted a simple change to an ansible playbook today. GPT-6-Astra/codex came up with the most convoluted, brittle solution possible the first time, even though it was extending and already clear, idiomatic playbook. It took some amount of offensive and critical prompting to get it to use ansible's built in modules and tooling to do the same job - and do so with nearly 80% less configuration and like 1000% more human readability.
Some part of me harbours a sneaking suspicion that the "throw everything at it" ethos is by design, not as a defensive measure against crappy code, but as a way to ensure there's so much code and it's so convoluted orgs and operators (or developers) are stuck/addicted.
It's still a force multiplier - but it's by no means driverless, especially for existing/already-running infra.
I work as a (depressed lol) sysadmin apprentice in a small MSP company (I live in Europe) and boy do I got a story about Ansible playbooks: We made an offer to one of our clients to automate the deployment of software to their computers (this is a client with around 150-200 employees, depending on whether you count only the "core" employees or also security and maintenance staff). Before we made and implemented this offer using Ansible, they did not have any sort of Software Deployment tool whatsoever, everything got installed fully manually.
(they also used to have local admin rights on all of their client computers until one employee got phished and literally gave away their personal ID card via a webcam)
In any case, guess who got to implement all the relevant playbooks for installing software and what tool they used for it? Our company literally handed the job to an intern who had no IT background whatsoever. I say this not to be mean, he was legitimately just at our company because a government program required him to do an internship.
He used Deepseek (our company does not believe in purchasing LLM subscriptions, at least not for us normal employees) to write literally all of the playbooks for any kind of software that mattered to our clients.
Now, as I said before, I am only an apprentice, and I am certainly not a good programmer by any means, but I read through parts of the Ansible documentation and had worked with it before, and I understood enough to at least be able to roughly judge whether a playbook made sense or was just way too complicated and convoluted.
I had to help this intern out multiple times, because he hadn't yet understood that, in order to write a functioning playbook, you first had to somewhat understand how to deploy a piece of software on a single test machine using CMD or Powershell syntax with an according .exe or .msi.
He simply prompted, pasted the playbook and then reprompted with the error codes from the failed playbook until it somehow worked or until I had to help him out.
This took place in December or November of last year and the playbooks are mostly still pretty shitty if I am being honest.
I did take away an important lesson from this "episode", though: LLMs can be very usefuly for writing code, or in this case, Ansible playbooks, but only if you have a somewhat decent and basic grasp of how software installation works via CMD/powershell and if you took the time to read through and learn about at least the basic Ansible concepts.
Since I am only an apprentice (on paper and in terms of my knowledge and how I get paid, not in terms of how much I am expected to earn for the company), I have painfully experienced how important it is to possess a certain level of understanding about the infra-related code and scripts that you would like LLMs to write for you, because otherwise it very quickly spirals out of control and starts throwing everything at the problem, just as you described.
Assuming AI agents are not the cause of the incident.
> This usually isn't a software quality issue... overcomplicated infrastructure failures cascading through a complex environment
That is a software issue.
Basically the number one issue these days
I don't consider fat-fingering a BGP route or a DNS entry to be a "software" issue directly.
Infra is >90% software nowadays
I blame bad vibes
> ... has been declining for a few years IMO
Interesting: there's a huge correlation with everybody beginning to use LLMs.
And we dismiss it as being non-causal by saying it all started going downhill before the advent of LLMs?
I don't buy it. I think we're seeing the results of what happens when you hand the keys of the kingdom to LLMs.
Using LLMs properly leads to better software, not just more of it.
I suspect some possible relation to SignDrop or attempts to patch it.
SignDrop is an unpatched Windows zero-day local privilege escalation (LPE) exploit that allows a standard user to gain NT AUTHORITY\SYSTEM privileges by abusing the Common Log File System (CLFS) kernel driver (clfs.sys). Security researcher Abdelhamid Naceri (also known as MSNightmare or Nightmare Eclipse) published a detailed technical write-up and functional proof-of-concept (PoC) code on GitHub on November 10, 2026.
Downdetector says LOTS of stuff is down. https://downdetector.com
Damn. That is crazy. The curve kinda looks like the curve that happens every november to the Google searches of "all I want for christmas is you"
Downdetector's methodology is pretty garbage. I'm always surprised to see techies referencing them.
It's something to reference. My view is that it's better than "doesn't load for me".
What's your preferred alternative?
The snarky but honest response is HackerNews/Reddit. But if you're trying for something that actually checks the sites you point it at instead of relying on users reporting "issues", a buddy of mine runs https://onlineornot.com/ and it seems generally more reliable.
Back in the golden days you could just go to search.twitter.com, search "AWS", and sort by recent.
Still can. AWS Status pages are still terrible. See HN for the outage a year ago https://news.ycombinator.com/item?id=45640838
> Still can.
No. It requires an account now, and they did away with the recent posts firehose.
"Start Free Trial" -- uh, no thanks. You seem skeptical of crowd sourcing. Enjoy your Encyclopedia Brittanica.
Ping?
Apparently Outlook, Gmail, etc are all working on the server at 192.168.1.1 then - ping says it's responding just fine
Full Disclosure, this is a Cisco product and I work there.
ThousandEyes Internet Insights offers a public outage map at https://www.thousandeyes.com/outages/ that is MASSIVELY more accurate (and faster to detect) than Down Detector because its based on actual telemetry and not on crowdsourcing.
Thank you for the recommendation!
They indicate sharepoint is getting blown out... again.
It is ironic that this outage map _also_ is not loading for me right now
Yes, just to confirm, it seems that our platform is getting hammered at the moment and it's causing the page to take a long time to load or intermittently load. We are looking into it.
https://status.thousandeyes.com/incidents/3tnqsbbgvw4x
it seems to be down... lol
still down :)
It seems like one of the best methodologies there is? Real people reporting real outages of a service they use?
I often know about outages dozens of minutes in advance of it being posted on official channels (or in the case of AWS, three days later...).
So what if the resolution is low because people can't log in to Fortnite and an Azure outage gets shown as an Epic Games outage. Doesn't matter. The live feed is incredibly reassuring from a "down for anyone else this instant, before official status page has a chance to see it?" Saves me so much time knowing whether it's a me-or-them issue.
How is it garbage? It's crowdsourced monitoring so sure, there will be false positives (especially when aws/cloudflare/azure/bgp services have a bad day), but it's one of the best indicators to quickly know if _something_ is going on.
Yeah, but the methodology means that normies are going to inaccurately blame AWS and Google (both are down right now according to downdetector)
At least it reports the numbers they are getting, you can see that outlook has 130k reports while AWS only has 1.3k.
not really, soon as i had a problem with outlook i went there and already saw user reports and a massive spike confirming it wasn't anything on my end.
As someone who ends up being unofficial downdetector-primary at a company, dealing with this shit and the fact that people cannot comprehend its mis-attribtion wastes so much of my time.
From what I've seen it seems people complaining they can't get emails from MS so that's why gmail is showing as down.
And with Google is people complaining Chrome doesn't load their "pages". I bet they mean outlook.
My housemate texted me saying our internet is so slow because outlook wasn't loading. So I think lots of people associate email not working with entire internet not working..
With how many people are unable to associate a "broken" monitor with an unplugged HDMI/DisplayPort or power cable, it doesn't surprise me that most people would not make a disctinction between the "internet" and "Outlook".
This happens every time there's an outage. People see their email not working and go there and mark everything as down regardless of whether it is affected or not. There's nothing wrong with Gmail or AWS or Cloudflare or Facebook.
"There's nothing wrong with . . . Facebook."
That's a bold claim to make on HN.
https://x.com/MSFT365Status/status/2120938282204688468
> We're investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas. More details can be found in the Microsoft 365 admin center under EX1550543.
GitHub the other day went down because of an influx of anonymous users. Microsoft has hinted that surging connections caused the outage. I wonder if these two are linked?
In my language many would say “descansito” :)
Outlook has been down for us for the last 2 hours
Same for me. Status won’t load even.
Personally I kinda enjoy these outages…
https://status.cloud.microsoft/ is very slow to load.
The page is showing a "Service Degredation" for "Microsoft 365 (Business or Enterprise)"
Updates below in reverse chronological order:
From the Thurdsay, November 12, 2026 at 7:30:36 PM UTC update:
Current status: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service.
---
From the Thurdsay, November 12, 2026 at 7:16:03 PM UTC update:
Current status: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've also moved traffic for some services off the affected infrastructure to further reduce load, with additional traffic moves in progress.
---
From the Thurdsay, November 12, 2026 at 6:59:24 PM UTC update:
Current status: We've completed redistributing connection traffic across our worldwide infrastructure, and we're moving additional traffic off the affected infrastructure to further reduce load. We're also restarting affected servers to return them to service. In parallel, we're investigating whether the elevated traffic reflects a genuine increase in requests or a shift in how traffic is being routed across our infrastructure.
---
From the Thursday, November 12, 2026 at 6:32:25 PM UTC update:
Title: Users may be unable to connect to multiple Microsoft 365 services
User impact: Users may be unable to connect to multiple Microsoft 365 services.
More info: Potentially impacted services include:
- Exchange Online
- Microsoft Teams
- SharePoint Online
- Microsoft Copilot 365
- Microsoft Defender XDR
Current status: We’re investigating an issue impacting multiple Microsoft 365 services and we've determined the affected infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. We're restarting and repairing impacted portions of this infrastructure to restore capacity, and reviewing an unexpected increase in a specific type of service traffic to determine whether it's contributing to the elevated load. In parallel, we're evaluating options to redirect traffic to alternate infrastructure to expedite relief.
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.
---
From the Thursday, November 12, 2026 at 6:10:02 PM UTC update:
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.
User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.
More info: Potentially impacted connection methods may include:
- Outlook on the web
- Messaging API (MAPI)
- Exchange ActiveSync (EAS)
- Representational State Transfer (REST) API
Current status: We’ve identified connectivity errors occurring on a portion of Exchange Online infrastructure which receives and processes users’ access requests. We’ve collected networking logs to review to further investigate the source of these errors and confirm our next steps.
Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.
Next update by: Thursday, November 12, 2026, at 8:00 PM UTC
---
Aside: What with the nature of the Teams, OneDrive, etc, products being Sharepoint and Exchange in a trenchcoat this is probably creating quite a mess for services besides Exchange Online, too.
Edit: Looks like the status page needs a status page.
Edit: Verified w/ multiple other parties that Teams and OneDrive are having issues, too. Interestingly, Microsoft 365 Family services are working fine. That makes me wonder if that product is running on separate infrastructure (or just hasn't caught fire yet).
Edit: The RSS feed seems to load fairly quickly: https://status.cloud.microsoft/api/feed/mac
502 The service behind this page isn't responding to Azure Front Door.
I was assured that with cloud we wouldn't have a single point of failure like we did on-premise. I must have fallen asleep at my desk.
That was never the promise. The nearest to that is the promise of multi-cloud or hybrid infrastructure, but neither of those have anything to do with outages of specific Microsoft services.
The "you can't possibly have better redundancy in your on-prem" was absolutely a sales pitch I heard to move to Microsoft 365.
The biggest site I work for, who went M365 hybrid last year, has incurred more Exchange downtime today than they had all of last year with their on-prem Exchange servers.
The service has redundancy, better than individual operators could provide on-prem. From the customer standpoint though, the service as a whole is a single point of failure: it either works or it doesn't.
It sounds like you are talking more about product reliability of M365 than you are about enterprise infrastructure reliability. M365 is a Microsoft product. M365 has no bearing on the credibility of cloud infrastructure as a whole, which is what your original comment spoke to.
Maybe not where you are but that's legitimately what our project managers were saying. We all knew better, of course.
YEah, that is not loading, along with the root status.cloud.microsoft , which MS links in their Xitter update [0]
What MS has posted so far:
>> Microsoft 365 Status >> @MSFT365Status >> We're investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas. More details can be found in the Microsoft 365 admin center under EX1550543. 12:54 PM · Nov 12, 2026
>> Microsoft 365 Status >> @MSFT365Status >> While we're working to mitigate impact, we've confirmed the issue may affect Microsoft 365 service connectivity for users in any region, more information will be provided in the Microsoft 365 admin center under EX1550543.
>> Microsoft 365 Status >> @MSFT365Status >> We've determined a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. We're providing more information under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as https://status.cloud.microsoft
>> Microsoft 365 Status >> @MSFT365Status >> 20m >> We've begun redistributing connection traffic across our broader worldwide infrastructure to help balance the load. More info under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as https://status.cloud.microsoft if the admin center is not available to you.
[0] https://x.com/MSFT365Status/status/2120938282204688468
anyone else just watch the admin portal post an update and then roll it back to the previous update....guess it didn't work. "We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service." was the old message from 7:52 UTC now it rolled back to 7:30 UTC update again
It looks much wider across aws, gcp? Whats going on?
Down for our whole organization as well.
Same here
bgp misconfigured or AI agent issues?
In cybersecurity we had black october, now we having black November it seems
currently the people who brought us black october are starting it!
https://downdetector.com/
A whole host of services are being effected. First glance, perhaps an AWS issue
I think a lot of ms orgs/window users may have external links blocked when defender is down. So it may appear other services are down.
Our Outlook doesn't work either
Can confirm. Down and out
email still not working, outlook
Affected in Mexico also, Azure seems fine still.
Yep my org as well.
It's funny how text-only niche forum that looks like it's running on RPi stuffed in someone's closet is routinely used to discuss active outages in multimillion/billion corps.
Maybe that's exactly why it's stable?
The M365 status page not loading reminds me of one of my favourite Simpsons jokes: https://www.youtube.com/watch?v=3Hz2uOSdV24
In the words of an ancient ...I think newgrounds(?) video embedded in a SWF, "I can't get to my email" Edit: here it is: https://www.youtube.com/watch?v=uRGljemfwUE
Hope this entertains you while we can't get to our emails.
how have i never seen this it is brilliant
Not sure they got the memo to host the status page in separate infrastructure...
I heard they moved it over to GH Actions. </sarc>
That would probably cost money or increase complexity, so I'm sure the idea was shot down.
Strangely, Teams chat is working fine here. Anything in Teams that is tied to other parts of O365, including the calendar, is dead. I'm currently watching a training video on sharepoint.com, so that's fine too, for now.
While I don't expect this to be the case, I'm emotionally prepared for this to be some sort of "dicks out for Harambe"-style action protesting JH's departure from Nvidia, on a larger and more technical scale.
Edit: Typo.
Did Anthropic's new release this week include an AI rollout plan (i.e. not approved by humans) to take down Office and Outlook for a lot of enterprises? I half-snarkily ask since we have seen "rogue AI" headlines before.
A fictional story about AI could be that it rolled out its new document, spreadsheet, slides, etc. apps, knows the IPO is coming up and decided to make a lot of opportunities for people to sign up for their new release by DDosing their competitor.
Neither email nor Teams is working at my non-tech megacorp employer. I wonder how much of the economy this is impacting.
My employer is very very close to MSFT. Both my employer and MSFT have been aggressively moving jobs to India, and firing people in the US. It's hard not to feel some schadenfreude.
Nice to see that intern finally learned not to push to prod on Friday.
Office 365 parts goes down all the time. Usually around 20:00 CEST time, not sure if that is prime change time over in the USA but very handy as it is usually fixed next day.
it's been down for over an hour globally
Yes? I know. I mean next workday for me :)
So in 10h
Now? I dont care Im logged off.
who puts their status page on servers the status is supposed to be for?
Fr lol
microsoft, apparently.
Maybe due to everyone pre-downloading GTA VI today ;-)
No worries, the AI was installing an update...now it's looking for the issue, found Exchange and deleted it...
i was gonna blame my isp but now i can see who bottlenecked my internet
But Linkedin is up! Yeah!
That are not the Druids your searching for...
https://azure.status.microsoft/en-us/status azure not down?
It's probably DNS.
my thoughts too
- outlook is down
- live.com is down
- onedrive loads the UI, but all of my contents are missing
- MS Edge sync is down (503s )
Yup, major-major outage.
Down
Relevant XKCD? https://xkcd.com/303/ (outages as modern compiler)
email doesnt work
GH and MS have been having a tough past couple weeks. Actions (hosted on shitty azure cloud) have been piss poor lately. I am honestly surprised GH and MSFT have the gall to continue advertising 99.9% uptime [1]
[1] https://github.com/customer-terms/github-online-services-sla
Three 9's is .36525 days per year. So if this one is resolved within 8 hours, that's about .999 uptime. (assuming they only have one such outage this year.)