- Outages - Outages Lists

CHTR/Spectrum - California West Coast
by robert.glover＠garlic.com 21 Aug '26

21 Aug '26

Looks like all Charter/Spectrum services (resi and biz (DIA/transit) are down on the West Coast. Word is there is a fiber cut in the Central Coast area, around King City due to a PGE pole down. No ETA provided at this point; anyone have any additional info?

1 0

NTT Sacramento Outage
by Nathan C 19 Aug '26

19 Aug '26

Some datacenter services are suddenly unavailable that are hosted near Sacramento on NTT's network - NTT's looking glass doesn't respond with that router selected, either. Anyone with more knowledge than me might have any insight?

4 4

[ADMIN] Outages lists and Acceptable Use Policy
by virendra rode 23 Jul '26

23 Jul '26

Mailing List Charter: The OUTAGES mailing list provides a forum for the timely exchange of information and technical discussion regarding major outages affecting critical Internet infrastructure. The list is intended to facilitate cooperation and knowledge sharing among network operators, Internet service providers, carriers, cloud providers, and infrastructure engineers worldwide. Topics appropriate for discussion include, but are not limited to: * Internet Exchange Points (IXPs) * DNS root servers and authoritative DNS infrastructure * Major carrier and backbone network outages * Cloud service provider outages * Data centers and carrier hotels * Central Offices (COs) * Submarine cable systems * Critical routing incidents (BGP, MPLS, Segment Routing, etc.) * Large-scale DDoS attacks affecting Internet infrastructure * Core blockchain infrastructure (e.g., Bitcoin nodes and supporting networks) * Other incidents that materially impact Internet availability, resiliency, or global connectivity The primary purpose of the list is to enable rapid information sharing, collaborative troubleshooting, post-incident technical analysis, and the exchange of operational best practices among the global network operations community. To ensure the mailing list remains a valuable technical resource, participation is governed by the following guidelines: 1. Discussion will focus on Internet / backbone related outages and technical issues surrounding it as described in the charter of OUTAGES. 2. Postings of issues inconsistent with the charter are prohibited. 3. Cross posting is prohibited. 4. Keep it concise when reporting. 5. Do not quote messages that were sent to you by other people in private mail, unless agreed beforehand. 6. Postings that include foul language, character assassination, and lack of respect for other participants are prohibited. 7. Product marketing is prohibited. 8. Postings of political, philosophical, religious and legal nature are prohibited. 9. Using list as source for private marketing initiatives is prohibited. 10. Autoresponders sending "out of office" or "vacation" mail either to the list or to the poster are prohibited. 11. Try not to flame; it is not polite. 12. Stay out of the drama and avoid confrontations. 13. Snarky members should be ignored. We all like lively debate but when it starts to get personal & nasty then it becomes very unpleasant. 14. Be kind to those who are kind to you. 15. Do not send "test" messages to determine whether your mail client is working. 16. Try to give back whenever you can. OUTAGES List FAQ: FAQ contributions are welcome -- please send email to admins(a)outages.org Mission: The primary goal of the OUTAGES mailing list is to facilitate the timely reporting and technical discussion of outages affecting major communications and Internet infrastructure with significant traffic- carrying capacity. The mailing list serves as a trusted forum where network operators, service providers, carriers, cloud providers, and infrastructure engineers can exchange operational information, share lessons learned, and collaborate during significant service disruptions. Our focus is on incidents that materially impact the availability, reliability, and resiliency of critical communications infrastructure. Community: The OUTAGES Volunteer Committee is comprised of experienced members of the global network operator community who volunteer their time to help administer and guide the mailing list. Outages.org is a community-driven initiative built by and for network operators. Its success depends on the collaboration, professionalism, and technical expertise of its members. For questions, suggestions, or administrative matters, please contact us at, admins(a)outages.org A. Is the list moderated? No, the outages mailing list is not moderated but we can be when 'code of conduct' is not being observed. B. When responding to outages(a)outages.org list, please keep your replies to the point pertaining to ongoing outages. For any POST outages related discussion, please direct them to outages-discussion(a)outages.org list in order to minimize the chatter. C. I am not getting any mail anymore from the list! Is it down or what? - If for any reason your email address is unavailable, after some retries you will be automatically unsubscribed. - You may get unsubscribed because MTAs relaying traffic to you get bounces for some reason. - There are no major outages to report :-) D. How do I report outages regarding outages mailing list? You could report problem(s) by reaching us at, admins(a)outages.org E. How do I subscribe / unsubscribe to OUTAGES Mailing List? For more information, * Outages-discussion mailing list outages-discussion(a)outages.org * Sign up for an account https://lists.outages.org/accounts/signup/ [1] * To subscribe send an email to outages-discussion-join(a)outages.org * To unsubscribe send an email to outages-discussion-leave(a)outages.org * To contact the list owners outages-owner(a)outages.org Archives: https://lists.outages.org/archives/list/outages-discussion@outages.org/late… https://lists.outages.org/archives/list/outages-discussion@outages.org/ [2] F. Disclaimer for the OUTAGES mailing lists? Read more about outages disclaimer, see below G. How can I reach the list admins? Please direct your queries to admins(a)outages.org Posting Policy: 1. The basic rule is to avoid asking questions that have been asked before, or that are irrelevant to other list users, or that are off topic. Please use your good sense. 2. Network operational related topics / issues are not appropriate for this forum. 3. Please read the FAQ and AUP (code of conduct) policy before posting for more details. Disclaimer for the Outages mailing lists: Public Archive and Legal Notice The OUTAGES mailing lists are public forums, and all mailing list archives are publicly accessible. The individuals who administer and contribute to the OUTAGES project do so solely in their personal capacities. This is a volunteer-driven community initiative and is not sponsored, endorsed, or affiliated with their respective employers or organizations. Public Distribution By sending an email to an OUTAGES mailing list, you acknowledge and agree that your message will be publicly distributed, archived, and made permanently available through the mailing list archives. Messages posted to the mailing list, including replies, are considered published communications under applicable United States law. While authors retain copyright ownership of their original content, submission to the mailing list grants OUTAGES the right to distribute and archive those messages as part of the permanent public record of the mailing list. Requests to remove previously published messages from the public archives will generally not be honored. The public nature of the mailing lists and their archives existed prior to your participation. It is your responsibility to determine the nature of the forum before submitting content. Copyright By posting material to an OUTAGES mailing list, you represent and warrant that: * You are the copyright owner of the material, or have obtained the necessary permission from the copyright holder to distribute it. * Alternatively, the material is in the public domain or otherwise lawfully available for redistribution. * Your submission does not infringe upon the intellectual property rights, privacy rights, or other legal interests of any third party. Disclaimer The opinions and information posted to the mailing lists are those of the individual authors and do not necessarily reflect the views of the OUTAGES project, its volunteers, or its contributors. OUTAGES does not verify, endorse, or guarantee the accuracy, completeness, or reliability of information posted by mailing list participants. To the fullest extent permitted by law, OUTAGES disclaims all warranties, express or implied, including but not limited to warranties of merchantability and fitness for a particular purpose. OUTAGES shall not be liable for any direct, indirect, incidental, consequential, or special damages arising from the use of, or reliance upon, information distributed through the mailing lists. Moderation OUTAGES is a community-driven technical forum and does not routinely monitor or exercise editorial control over mailing list discussions. However, the OUTAGES Volunteer Committee reserves the right to moderate discussions, reject postings, suspend posting privileges, or remove participants who violate the mailing list Code of Conduct or otherwise disrupt the purpose of the community. Please send your feedback, comments and /or recommendations on how we can improve outages services further at admins(a)outages.org Thank you for your trust -- regards, admin team [1] https://lists.outages.org/accounts/signup/ https://lists.outages.org/accounts/signup/](https://lists.outages.org/accou… [2] https://lists.outages.org/archives/list/outages-discussion@outages.org/ https://lists.outages.org/archives/list/outages-discussion@outages.org/](ht…

2 2

Apparently Equifax is down for consumers and businesses.
by Chapman, Brad (NBCUniversal) 13 Jul '26

13 Jul '26

I was ordering fiber optic internet from Frontier Communications—my doctor said I should consume more fiber—but their system said my credit check failed and was demanding an equipment deposit. I pushed back. They ran it three times. Then they got word in a group chat that Equifax’s consumer and business portals are down, so they can’t process any credit checks. Woe be unto you if you work in finance or support a business that depends on this service. I hope they didn’t have another breach. Maybe they will need a tiny excavator to dig them out of this mess like that freighter stuck in the Suez canal<https://www.reddit.com/r/CatastrophicFailure/comments/mcw8og/new_pictures_f…> for the last two days... Cheers, Brad

8 7

Twelve99 - Major packet loss
by Phil Lavin 02 Jul '26

02 Jul '26

Hi folks, Seeing major packet loss on 1299. Somewhere between Seattle and Chicago. mtr below between AWS usw2 and Hetzner Germany. My traceroute [v0.95] ** (**) -> hc-ping.com (176.9.71.146) 2026-07-02T09:06:23+0000 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. ip-**.us-west-2.compute.internal 0.0% 81 0.2 0.2 0.2 0.3 0.0 2. 242.11.42.7 0.0% 81 8.2 9.4 8.0 20.0 2.6 242.11.42.5 242.11.43.5 242.11.43.135 242.11.42.129 242.11.43.3 242.11.42.131 242.11.42.3 3. amazon-ic-341989.ip.twelve99-cust.net 0.0% 81 7.6 7.6 7.5 7.9 0.1 4. sea-b1-link.ip.twelve99.net 0.0% 80 9.4 9.1 8.3 14.5 1.1 5. chi-bb2-link.ip.twelve99.net 67.1% 80 175.5 174.2 171.2 176.8 1.8 6. ewr-bb2-link.ip.twelve99.net 56.2% 80 112.3 112.3 110.2 113.4 0.7 7. ldn-bb2-link.ip.twelve99.net 54.4% 80 205.7 205.6 204.7 207.3 0.6 8. hbg-bb2-link.ip.twelve99.net 60.8% 80 204.2 204.0 202.6 205.5 0.7 9. hbg-b2-link.ip.twelve99.net 62.0% 80 191.9 192.6 190.4 203.8 2.7 10. hetzner-ic-383976.ip.twelve99-cust.net 55.7% 80 201.4 201.3 198.8 203.0 0.8 11. core21.fsn1.hetzner.com 38.8% 80 201.1 200.8 199.6 202.0 0.6 12. ex9k2.dc6.fsn1.hetzner.com 55.7% 80 201.4 201.4 199.7 206.8 1.1 13. static.146.71.9.176.clients.your-server.de 41.2% 80 201.7 201.3 199.2 202.6 0.7

5 5

US Bureau of Industry and Security website down?
by Aryeh Goretsky 01 Jul '26

01 Jul '26

Hello, Tried visiting the BIS[.]GOV website and it is not loading. Tried a few pages in my browser's history (https[:]//www[.]bis[.]gov/about-bis and https[:]//www[.]bis[.]gov/news-updates) and received the following error: 502 Bad Gateway Microsoft-Azure-Application-Gateway/v2 Getting a 524: A Timeout Occurred error when attempting to visit https[:]//www[.]bis[.]gov/regulations/ear (also via my web browser's history). I am connecting from the Comcast/Xfinity network, not that I believe that makes any difference. Regards, Aryeh Goretsky

3 3

Another FTR fiber cut
by William Kern 05 Jun '26

05 Jun '26

Wonder if it was the same idiots ** Here is the latest update on the issue impacting your services: Update, Be advised, work to repair cable is continuing at this time. Team is reporting that cut was caused by vandalism. ETR is not yet available. Further updates to follow as more information becomes available. William Kern PixelGate Networks

2 2

Frontier issue southern cal
by William Kern 12 May '26

12 May '26

After an hour on the hold and never hearing back from about the WebTicket I had created on their support portal. I was able to get a rep to confirm a general issue "in the region". She mumbled about getting lots of calls, so I'm not sure of the blast radius. We are in Thousand Oaks. I hope this isn't another one of those "idiots can't tell the difference between fiber and copper" cuts. William "Bill" Kern PixelGate Networks

3 9

.de DNS resolution outage
by Sadiq Saif 05 May '26

05 May '26

Seeing multiple DNS resolution failures of .de domains, all returning SERVFAIL. Large German news site heise.de is currently no longer resolving in the DNS amongst others. -- Sadiq Saif https://nullrouted.space

2 1

AWS recovering a bit after losing AZ in me-central-1
by Paul M - outages 13 Mar '26

13 Mar '26

https://health.aws.amazon.com/health/status Service Multiple services Severity Degraded RSS Increased Error Rates Mar 01 7:09 AM PST We wanted to provide some additional information on the isolated power issue. At this time, most AWS Services have weighted away from the affected Availability Zone (mec1-az2) and are seeing recovery for their affected operations and workflows. For EC2 Instances, EBS Volumes, and other resources that are impacted in the affected Zone, we will have a longer tail of recovery. At this time, power has not yet been restored to the affected AZ. For now, we recommend continuing to retry any failed API requests. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or replace affected resources by launching replacement resources in one of the unaffected zones, or an alternate region. As of this time, recovery is still several hours away. We will provide an update by 8:30 AM PST, or sooner if we have additional information to share. Mar 01 6:09 AM PST We can confirm that a localized power issue has affected a single Availability Zone in the ME-CENTRAL-1 Region (mec1-az2). EC2 Instances, DB Instances, EBS Volumes, and others resources are currently unavailable and will experience connectivity issues at this time. Other AWS Services are also experiencing error rates and latencies for some workflows. We have weighed away traffic for most services at this time. We recommend customers utilize one of the other Availability Zones in the ME-CENTRAL-1 Region at this time, as existing instances in other AZ's remain unaffected by this issue. We are actively working to restore power and connectivity, at which time we will begin to work to recover affected resources. As of this time, we expect recovery is multiple hours away. We will provide an update by 7:15 AM PST, or sooner if we have additional information to share. Mar 01 5:19 AM PST We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mec1-az2) in the ME-CENTRAL-1 Region due to a localized power issue. Existing instances in this zone will also be affected. Other AWS Services may also be experiencing increased errors and latencies for their workflows, and we are working to route requests away from this affected Availability Zone. We recommend customers make use of other Availability Zones at this time. Targeting new launches using RunInstances in the remaining AZs should succeed. Existing instances in the other AZs are not affected. Mar 01 4:51 AM PST We are investigating issues with AWS services in the ME-CENTRAL-1 Region.

3 12