- Outages - Outages Lists

bgp.he.net
by John Kristoff 04 Apr '23

04 Apr '23

IP connectivity appears to be OK, but the web-based service for HE's BGP toolkit page appears to be unavailable at the moment. I've not been monitoring or have insight into their network status, but presumably this is a temporary, transient issue for those that use the service. John

2 1

Spectrum down (TV and internet)
by Andy Ringsmuth 01 Apr '23

01 Apr '23

I’m not a Spectrum customer but it sounds like they are down possibly nationwide for TV and Internet according to various DownDetector type sites. Several of my neighbors mentioned it was down. https://istheservicedown.com/problems/charter-communications/map Sent at 9:49 am CDT. ---- Andy Ringsmuth 5609 Harding Drive Lincoln, NE 68521-5831 (402) 202-1230 andy(a)andyring.com

4 4

Spectrum down (TV and internet)
by Andy Ringsmuth 01 Apr '23

01 Apr '23

I’m not a Spectrum customer but it sounds like they are down possibly nationwide for TV and Internet according to various DownDetector type sites. Several of my neighbors mentioned it was down. https://istheservicedown.com/problems/charter-communications/map ---- Andy Ringsmuth 5609 Harding Drive Lincoln, NE 68521-5831 (402) 202-1230 andy(a)andyring.com

5 4

FAA.gov nameserver outage
by Michael Loftis 31 Mar '23

31 Mar '23

Looks like faa.gov's nameservers are all having a bad time, only occasionally responding right now from multiple tests from my home network, datacenter POPs (Seattle, Chicago), and 8.8.8.8 -- "Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds." -- Samuel Butler

14 22

Comcast public-facing DNS servers unreachable
by Jeremy Chadwick 31 Mar '23

31 Mar '23

Looks like Comcast's public-facing DNS servers aren't responsive. MXToolbox and a couple other DNS-related sites confirm this, but a simple dig +trace is sufficient as well. $ dig +trace pop3.comcast.net {snipping for brevity} ;; Received 1173 bytes from 192.203.230.10#53(e.root-servers.net) in 11 ms comcast.net. 172800 IN NS dns101.comcast.net. comcast.net. 172800 IN NS dns102.comcast.net. comcast.net. 172800 IN NS dns103.comcast.net. comcast.net. 172800 IN NS dns104.comcast.net. comcast.net. 172800 IN NS dns105.comcast.net. comcast.net. 86400 IN DS 40909 5 2 30C0F50E68DCC9A2F279A994C07CF22CED97AADF44C2B1FE38A1B32B A1A34174 comcast.net. 86400 IN DS 40909 5 1 DDC19733884EE533B35B4B57717BEA9B0EF2C4D1 comcast.net. 86400 IN RRSIG DS 8 2 86400 20230404061502 20230328050502 27254 net. btO4iRmoCjqgYlgZPCORiX7soM6Twg610wTSCdD/sxizsoLoWeB+vBXY mChMJmrhGenkhJroQoriY1FyMDl4EvcTyKRDYG3c8HL0p8ILo4kJAOWi CSAt/qB76i21+8SmLsvhE0bPuUUQQXv69vfDfjxxYVsAbbMGfTLvHNJT BX3B6CrqNzXARN2dpDaUsb/8r3i0ve9byu/Sur2vZIYjwg== couldn't get address for 'dns101.comcast.net': not found couldn't get address for 'dns102.comcast.net': not found couldn't get address for 'dns103.comcast.net': not found couldn't get address for 'dns104.comcast.net': not found ;; Received 649 bytes from 192.48.79.30#53(j.gtld-servers.net) in 15 ms -- | Jeremy Chadwick jdc_at_koitsu.org | | UNIX Systems Administrator PGP 0x2A389531 | | Making life hard for others since 1977. |

3 4

O365 geolocation server issue
by Ryan McGinnis 23 Mar '23

23 Mar '23

1 0

Reddit down 14 Mar 2023
by Andrew J. Caines 14 Mar '23

14 Mar '23

As of a few minutes ago, no response from www.reddit.com = reddit.map.fastly.net = 151.101.45.140 for me. Reports are rising rapidly on https://downdetector.com/status/reddit/ -- -Andrew J. Caines- Unix Systems Architect A.J.Caines(a)halplant.com "Machines take me by surprise with great frequency" - Alan Turing

4 3

Hurricane @ Chicago CH1 BGP Down
by Nate Burke 09 Mar '23

09 Mar '23

I lost my Hurricane IPV4 BGP Session to CH1, however Other IPv4 Traffic on the same HE port is fine, as is IPv6 BGP. Connection to Hurricane CH2 is Stable. NOC says that there's an ongoing maintenance event due to a large traffic spike. But has no other updates. Anyone else seeing issues in CH1?

1 1

4.2.2.2 down in LA area
by jd 08 Mar '23

08 Mar '23

been down for maybe 30-45 minutes tried it from spectrum fiber, att fiber, my fiber, everyone's fiber, dying at level3 for me, works from digitalocean up north though. tried from some other random vps and it's down there too, no queries, no mtr but queries working from digitalocean. as i was writing this email, i'm seeing it responding to ping here and there but no dns yet

7 7

Verizon FIOS IPv6 routing issue
by Robert Blayzor 07 Mar '23

07 Mar '23

This issue seems to crop up from time to time and it takes days for Verizon to finally get their act together and fix it. Upstate NY Verizon FIOS IPv6 routing seems to be broken. I can get 3-4 hops out into Verizon before it dies. Similar traces off net to my IPv6 prefix just dies in their network and never gets to me. Verizon FIOS frontline support is completely useless to escalate this issue and can't talk to anyone who is not understanding because it's not on the support script. Does anyone have a Verizon/FIOS NOC or know someone VZ NOC/engineering that can look into this. It's been a few days. The last time this happened (for several days) it stayed fix for a while, now it's back. It's like VZ is missing routes... My IPv6 PD 2600:4040:561f:ff::/56 From FIOS to google: traceroute6 to www.google.com (2607:f8b0:4006:80e::2004) from 2600:4040:561f:ff01:20c1:18c9:d440:24ff, 64 hops max, 12 byte packets 1 2600:4040:561f:ff01::1 3.265 ms 4.194 ms 3.578 ms 2 2600:4040:5610::1 10.472 ms 9.278 ms 14.681 ms 3 2600:4000:1:134::14 21.434 ms * 21.067 ms 4 * * * 5 * * * 6 * * * From off net to FIOS; tracing the route to 2600:4040:561F:FF01::1 ... 15 msec 15 msec * 9 * * oak-agg8.cenic.net (2607:F380::118:9A41:231) 48 msec 10 * * * 11 * 2600:807:A0F::A5 115 msec * 12 2600:807:A0F::A5 [AS 701] 115 msec * 68 msec 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * BGP route exists but doesn't complete... Routing entry for 2600:4040:5000::/36 Route count is 1/1, share count 0 Routing paths: 2600:803::15 MPLS label: nolabel Last updated 4d14h ago I can ping the first two hops outside my home network; wondering if anyone else in FIOS land can get to 2600:4040:5610::1 ? Anyone else run into similar issues? Kind of a pain to have this broken, the only way to fix this is to disable IPv6 everywhere on my inside network at home... -- inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP: https://pgp.inoc.net/rblayzor/

1 0