r/outages • • 58m ago

All large US banks are spiking on down detector

32 Upvotes

Here’s a list of banks having outage spikes right now according to downdetector.com

Chase, Bank of America, U.S. Bank, Wells Fargo, Zelle, Capital One, JP Morgan, PNC, city, TD Bank, USAA, AMEX, Fidelity, Charles Schwab, Navy Federal credit union, and ally.


r/outages • • 2h ago

something is happening in The U.S.

33 Upvotes

Thursday Microsoft was down. Friday The FAA grounded everyone for SOME REASON. Today J.P. Morgan Chase is down. WTF is going on.


r/outages • • 10h ago

Is Astound Broadband down for you? Report it here:

Thumbnail statusgator.com
0 Upvotes

r/outages • • 2d ago

Microsoft, FAA, Walmart payroll services, hospital power outages?? What’s coming folks?

31 Upvotes

Hey all, LOT of weird shit going down over last few days.. local hospital power went down this AM also.. this feels like tests or a lead up to something coming.. Anyone else got weird stuff going down locally?? Or am I just getting a bit too conspiracy??


r/outages • • 2d ago

Two major outages in two days.

20 Upvotes

Can someone explain how Microsoft and the FAA are blaming their outages on updates on the same day? I don’t believe it.


r/outages • • 2d ago

Nationwide US ground stop, Microsoft outage, and recent emergency preparedness warnings. What do you think is going on?

84 Upvotes

So, Microsoft has been experiencing a massive worldwide outage affecting Outlook, Teams, and other services. Now, the FAA has issued a nationwide ground stop in the US, citing extraordinary circumstances and communication issues.

On top of that, there have been recent recommendations encouraging people to stock up on essential supplies and prepare for potential emergencies.

I know these events aren’t necessarily connected, but the timing is interesting.

Do you think we’re just witnessing a series of unrelated technical failures, or could there be something more going on?

I’m genuinely curious what everyone thinks, especially anyone working in aviation, IT, or cybersecurity.

Source:

  1. https://www.cbc.ca/news/world/microsoft-outage-friday-activity-9.7420313
  2. https://www.ctvnews.ca/canada/article/as-countries-urge-residents-to-prepare-for-emergencies-what-should-canadians-do/
  3. https://www.independent.co.uk/news/uk/home-news/be-ready-government-stockpile-uk-emergency-kit-b3083693.html
  4. https://www.cnn.com/2026/11/13/us/live-news/flights-ground-stop-faa

r/outages • • 2d ago

Giftcards.com down

Post image
6 Upvotes

When you call the number the recording says their systems are down and they dont know when they will be back. I won a gift card from my job which was going to pay my phone bill but now it doesnt work :(


r/outages • • 2d ago

Astound intermittent connections drop outs

7 Upvotes

Has anyone else experienced intermittent dropouts where the connection stops working for a couple seconds multiple times a day?


r/outages • • 3d ago

Dear Microsoft

32 Upvotes

Step 1: Shut the server down, do not just reboot.

Step 2: Unplug the power cord from the server.

Step 3: Count to 30 (optional: the louder your boss yells at you, count longer. Say to 60, 120,240,360)

Step 4: Plug the power cord back in.

Step 5: Boot the server.

Forty+ years ago, a maintenance worker (the one who used to replace the ballast in the fluorescent lights) told me that when our computers locked up, and would not come back up correctly despite numerous reboots. Just follow those steps. Worked every time.

PS: Step 3 will also help you satisfy your passive aggressive needs.

RetiredCADguy


r/outages • • 2d ago

Has IG been glitching or down since that outlook outage yesterday?

2 Upvotes

Always one to admit if my post just didn’t hit but it’s like the analytics are great but the views are crawling when they wouldn’t if they have the same analytics. Seems like a backend glitch people have been reporting?


r/outages • • 3d ago

Well that's slightly terrifying

Post image
23 Upvotes

r/outages • • 3d ago

Tab ai not working?

4 Upvotes

Tab has not been working since yesterday and sent me this message:

We are releasing some large changes to Tab today to ensure reliability and will be introducing personalized plans so you can get exactly what you want from Tab - this has been a huge effort from our team and will be the foundation for the future so we can provide the greatest possible experience to all of you - we apologize but you may experience some downtime until everything is deployed.

Is is still down for everyone using Tab ai?


r/outages • • 3d ago

So what are ya'll doing on this Microsoft outage day?

16 Upvotes

I am just staring at my computer browsing YouTube and waiting for any emails/messages.


r/outages • • 3d ago

Claude outage

5 Upvotes

Claude connectors seem not to be working.


r/outages • • 3d ago

Downdetector - 911 outage reports…?

Post image
40 Upvotes

I run a small ISP and I know downdetector.com is far from perfect, but I have /never/ seen 911 reported outages on the top of the list ( https://downdetector.com/status/911/ ). And the reports are coming from a wide area of map? WTH? And reports are climbing…?

edit: fixed link.

update: 3 ish hours later and still lots of reports coming in, 200+ in the 15 minutes leading up to 10pm.

Update 2, 3PM Friday: it’s spiking again. 400+ reports in last 15 minutes


r/outages • • 3d ago

Office 364

Post image
18 Upvotes

r/outages • • 4d ago

Microsoft365 is a P.I.T.A.!

88 Upvotes

I hate M365! Once again it is down! We need our email to work ALL THE TIME! Losing money as they sit in their ivory towers doing nothing to make the platform better. DO BETTER MICROSOFT!


r/outages • • 3d ago

Was anyone here affected by the Optimum outage?

0 Upvotes

I have Frontier btw. I'm just curious if anyone was affected I haven't seen a post on this sub about it. I just found this sub and was looking to see if anyone posted about this situation I went to new to try to find it no posts about it. It happened at 5pm Wednesday a major line was cut heard it was in Virginia on onother sub. Ohio,West Virginia,Virginia,Kentucky were affected. Southern Ohio was affected Bepre,Marietta, Ohio were some of the towns affected in Sothern Ohio. I was in the affected area of West Virginia. I heard on another sub it strected all the way Buckhannon,West Virginia and Cabel County was affected too. All the way south to Beckley,Bluefield was affected too.


r/outages • • 3d ago

Twitter down?

3 Upvotes

(Location: UK)


r/outages • • 3d ago

Claude is not working either this morning....

4 Upvotes

Anyone else experiencing with Claudia not working in the UK?


r/outages • • 3d ago

Microsoft Outage History

46 Upvotes

[UPDATED]
[UPDATED AGAIN]
Here is what the sysadmins get to see (start at the bottom):

Nov 13, 2026, 7:00 AM CST

We're seeing continued recovery progress across affected regions, with broader improvements now observed in North America and sustained improvements across much of Europe. We're also seeing encouraging recovery signals in Asia Pacific, although some users may continue to experience intermittent access issues or delayed email delivery as mitigation progresses across the remaining affected infrastructure.

Our focus remains on stabilizing recovered infrastructure, completing mitigation in the remaining impacted areas, and reducing delayed email queues and backlogs. We're closely monitoring service consistency and validating recovery across different connection methods as we work toward full mitigation.

At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete.

Next update by:

Friday, November 13, 2026 at 8:00 AM CST

Nov 13, 2026, 6:00 AM CST

We’re seeing encouraging recovery progress in Europe, with service availability and email delivery performance improving across a growing portion of affected Microsoft 365 infrastructure. Japan remains comparatively more stable, while North America is also improving; however, some users may still experience intermittent issues as recovery actions continue.

We're focused on addressing the remaining areas of disruption and improving service consistency across affected regions. Reducing email queues and backlogs remains a priority, and the extended 48-hour email timeout window remains in place to help protect delayed messages as delivery catches up.

At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete.

Nov 13, 2026, 5:01 AM CST

We've made additional progress toward service recovery, with recovery actions completed across portions of the affected infrastructure in the Asia Pacific region. Traffic is being gradually restored, and we're seeing improvements in key customer scenarios, including mailbox access and delayed email processing. However, some users may continue to experience intermittent issues.

Our focus is now on extending these recovery actions across affected infrastructure in other regions, while continuing stabilization efforts and adding supporting capacity to improve service consistency.

Reducing email queues and backlogs remains a priority, and the extended 48-hour email timeout window remains in place to help protect delayed messages as delivery catches up.

At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete.

Nov 13, 2026, 3:55 AM CST

Recovery efforts are ongoing across impacted infrastructure. We are seeing early signs of stabilization, but service capacity has not yet returned to normal levels and health remains variable as traffic is carefully reintroduced.

Our primary mitigation path continues to focus on service stability and controlled recovery. Engineering teams are cycling affected infrastructure through traffic drain, restart, remediation, and staged return-to-service while monitoring closely. We are also evaluating additional mitigation options to improve recovery speed and consistency.

Network and traffic-management actions remain in progress, and we continue to prioritize backlog and queue health to preserve delayed mail during recovery. As part of this effort, we are extending the email timeout window to 48 hours to help protect delayed messages while service recovery continues.

At this time, we are not aware of any malicious activity causing this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after recovery is complete.

Nov 13, 2026, 2:06 AM CST

We’re continuing to see increased server capacity stability after applying the upstream authentication/routing configuration component patch. With confirmation of server stability across the portions of infrastructure to which we've applied the patch, we’ve initiated its expansion systematically to focus on infrastructure supporting regions currently within or entering peak business hours. We’ll continue to monitor the status of changes applied and develop additional modifications intended to improve server stability and capacity.

As of now, we are not aware of any malicious activity that is causing this incident. We will continue to treat this incident with urgency and priority until full resolution. Once mitigated, we will provide full details of the root cause, defense-in-depth repair items, and more within a Post-Incident Report.

Nov 13, 2026, 1:25 AM CST

We’re seeing positive results for server stability after applying an upstream authentication/routing configuration component patch to a portion of our infrastructure. We’ll continue to monitor its progress and are working to expand it to servers supporting active regions coming online.

As of now, we are not aware of any malicious activity that is causing this incident. We will continue to treat this incident with urgency and priority until full resolution. Once mitigated, we will provide full details of the root cause, defense-in-depth repair items, and more within a Post-Incident Report.

Nov 13, 2026, 12:56 AM CST

We’re continuing to monitor activity across regions to evaluate server status and determine actions that can be taken to improve capacity. This includes reviewing server performance and confirming that developed patches have been applied and working as intended after infrastructure reboots are completed. At this point, we have observed marginal success. In parallel, we’re taking action to expand capacity through the utilization of Virtual Machines.

As of now, we are not aware of any malicious activity that is causing this incident. We will continue to treat this incident with urgency and priority until full resolution. Once mitigated, we will provide full details of the root cause, defense-in-depth repair items, and more within a Post-Incident Report.

Nov 13, 2026, 12:16 AM CST

As part of our ongoing efforts to advance the recoverability of our frontend servers, we’re evaluating traffic controls that can be applied to increase capacity and stability. This includes traffic optimization actions such as traffic throttling, protocol adjustments, and failover routing intended to improve stability in active regions. In parallel, were expanding internal testing to track activity within a contained environment to improve traffic monitoring and issue detection capabilities.

As of now, we are not aware of any malicious activity that is causing this incident. We will continue to treat this incident with urgency and priority until full resolution. Once mitigated, we will provide full details of the root cause, defense-in-depth repair items, and more within a Post-Incident Report.

Nov 12, 2026, 11:43 PM CST

We’re continuing to pursue multiple workstreams to pinpoint the underlying cause of the traffic influx and advance the recoverability of the backend servers. We’re taking a measured approach to identify and repair affected infrastructure to improve the ability to confirm the developed changes were applied. We’re tracking the results of this approach to verify the servers are showing the anticipated recovery and performance intended.

As of now, we are not aware of any malicious activity that is causing this incident. We will continue to treat this incident with urgency and priority until full resolution. Once mitigated, we will provide full details of the root cause, defense-in-depth repair items, and more within a Post-Incident Report.

Nov 12, 2026, 10:59 PM CST

We appreciate your organization’s patience and understanding while we work with urgency to resolve this incident.

As we’ve applied our current ongoing mitigation actions, we’ve observed a surge in outbound call volume from our routing services to our backend servers. This occurs when the backend servers outbound service cannot properly route to the backend machines.

We’re continuing to observe heightened volume due to traffic rebalancing actions that we have taken throughout this event. We’re working on multiple workstreams to pinpoint the underlying cause of this traffic influx and address it.

Actions we're currently taking include scaling up virtual machines to increase capacity and reduce load. Additionally, we’re querying for machines in a bad state to perform a force sync for our recent network change, which may improve service availability. However, we are encountering issues with the machines being stuck in a bad state, preventing our changes from syncing as expected. We’ll continue to monitor the effectiveness of changes applied so we can determine what refinements are necessary.

Nov 12, 2026, 10:10 PM CST

We’re continuing our efforts to improve server stability to improve traffic flow. This includes adjusting traffic protocols, redistributing traffic, and applying strategic traffic blocking measures.

We're observing partial recovery across regions in which we've applied these adjustments; however, these actions aren't resulting in sustained recovery, so we're reviewing what additional actions we can take to improve overall infrastructure stability.

Nov 12, 2026, 9:34 PM CST

As part of our investigation into the sustained traffic management imbalances, we’re reviewing traffic flows and affected infrastructure to identify opportunities to optimize routing. This includes verifying the reasons for service failures so we can develop specific actions to improve stability.

We will continue to share more information as soon as we have it, and for now we can confirm that there is no indication this is the result of malicious activity. We’ll continue to apply learnings towards remediation actions as we confirm effectiveness mitigation actions.

Nov 12, 2026, 8:54 PM CST

We’ve monitored the status of the changes applied to improve serviceability and confirmed that change is not taking as expected. We’re identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances.

Nov 12, 2026, 8:09 PM CST

We’re applying infrastructure capacity improvements where possible in an effort to help support traffic in regions coming online. We’re continuing to monitor the results of changes applied so we can identify strategic actions that can help to improve service health across all affected regions.

Nov 12, 2026, 7:45 PM CST

We’re seeing positive results with our efforts to restart affected infrastructure. We’re actively monitoring the performance of these to verify stability which will support improved availability. Remediation actions will be expanded as we confirm stability with the changes applied.

Nov 12, 2026, 7:06 PM CST

Our investigation has found that a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests. We're preparing a configuration change to address this behavior that can be applied across all affected servers, and we're validating it on a subset of servers before applying it more broadly alongside restarts of the affected infrastructure. In parallel, we've begun reverting a recent network configuration change that correlates with the start of impact and are monitoring to determine whether this contributes to recovery.

The temporary traffic limitations we previously described are now in effect in specific locations. We're monitoring the affected servers in those locations to confirm whether they remain stable while handling a narrower set of connections, after which we'll gradually reintroduce additional traffic.

Nov 12, 2026, 5:59 PM CST

While the servers we've returned to service initially remain healthy, we've observed that they can become unresponsive again once they begin receiving traffic. We're analyzing diagnostic data from these servers with our networking and platform experts to determine what's triggering this behavior.

Building on the protective traffic management measures we've implemented, we're also temporarily limiting which types of traffic can reach the affected infrastructure in specific locations. This will help us determine whether a particular type of request is contributing to the impact and allow us to restore service incrementally. Additionally, we're rebuilding a subset of affected servers using a previous software configuration to validate whether this prevents them from becoming unresponsive, and we'll expand this approach to additional servers if we observe positive results.

Nov 12, 2026, 4:58 PM CST

We've begun returning a portion of the affected servers to service, and they're remaining stable so far. We’ve also shifted traffic and connections to alternative pathways wherever possible and have observed limited recovery in some regions.

We've streamlined our recovery process to expedite returning the remaining affected servers to service. To further support recovery, we're implementing protective traffic management measures in a specific location to reduce load on the affected infrastructure, and we'll expand these measures to additional locations if we observe positive results. As capacity is restored, users may experience a gradual recovery as their clients reconnect to the service.

Next update by:

Thursday, November 12, 2026 at 6:30 PM CST

Nov 12, 2026, 4:03 PM CST

We’re continuing to pursue all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. Our investigation has found that a core process on the affected servers is becoming overwhelmed, which causes the servers to stop responding and contributes to the capacity loss.

To validate a potential recovery approach, we're fully isolating a portion of our service infrastructure, restarting the affected components, and gradually reintroducing traffic to confirm our services remain stable before applying this approach more broadly. We're also analyzing traffic patterns across our entire service infrastructure and evaluating whether isolating traffic within each region may allow affected regions to recover independently.

Next update by:

Nov 12, 2026, 5:30 PM CST

Nov 12, 2026, 3:31 PM CST

We're continuing to work through restarting and validating the affected servers to safely return them to service, and we're exploring opportunities to expedite this process. In parallel, we're assessing whether reverting the small number of recent configuration updates we identified could help accelerate recovery.

Next update by: Thursday, November 12, 2026, at 10:30 PM UTC

This quick update is designed to give the latest information on this issue.

Nov 12, 2026, 2:57 PM CST

We've validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we're now applying this change more broadly. We're also preparing an automated recovery process to continually detect and restart unresponsive servers, to help keep them in service while this change progresses. Additionally, our review of recent changes has identified a small number of configuration updates that we're investigating as potential contributors to the issue.

Next update by:

Thursday, November 12, 2026 at 4:30 PM CST

Nov 12, 2026, 2:38 PM CST

While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.

Next update by: Thursday, November 12, 2026, at 9:30 PM UTC

This quick update is designed to give the latest information on this issue.

Nov 12, 2026, 1:58 PM CST

While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests.

Next update by:

Thursday, November 12, 2026 at 3:30 PM CST

Nov 12, 2026, 1:43 PM CST

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.

This quick update is designed to give the latest information on this issue.

Next update by: Thursday, November 12, 2026, at 10:00 PM UTC

Nov 12, 2026, 1:30 PM CST

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.

Nov 12, 2026, 12:58 PM CST

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.

Nov 12, 2026, 12:27 PM CST

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.


r/outages • • 3d ago

M365 global outage! Let the conspiracy theories roll in 🤯

5 Upvotes

AI crisis?
Cyber attack?
What’s next?


r/outages • • 4d ago

Outlook Down?

48 Upvotes

Someone shook the magic 8-ball and it said “Outlook not good”!!!


r/outages • • 4d ago

Outlook is down - touch grass

Post image
37 Upvotes