Outage following sched maintenance Berkeley

[tigertech]

As of 9:34am, there's no mention of this outage at https://sonicstatus.com . Sonic should post a message there.

Yep. What's the point of an outage page if it's not being used even when Sonic is aware of the outage? Frustrating, because I have that page bookmarked on my phone and that's where I was looking.

[spencerw]

We apologize for the inconvenience and disruption this outage has caused. We do our best to communicate outages as soon as they are identified and we can confirm what customers are impacted by it but that process can take some time. We have made a lot of improvements recently to our outage process however we are still working to make it more accurate and faster/more efficient. Since MOTD's go out to every customer, they are not posted for every outage, only the ones that impact large portions of our customer base. For smaller outages, we send email and SMS updates only to the customers who are actually impacted. We certainly understand the frustration outages and having to wait for updates/information can cause. We will continue to work improve on all aspects of our outage process.

[tigertech]

Hello, this is Sonic with some good news! The outage affecting our equipment in the Albany area has been resolved successfully.

Do others who were affected by this have working IPv6 connectivity? Only IPv4 works for me now (even after rebooting my router). I don't appear to be getting allocated an IPv6 address, even though Sonic's Juniper router advertises its link-local fe80:: address as a router:

Code: Select all

$ ip neigh | egrep b4:8a:5f:98:fe:94
23.93.80.1 dev eth0 lladdr b4:8a:5f:98:fe:94 REACHABLE
fe80::b68a:5fff:fe98:fe94 dev eth0 lladdr b4:8a:5f:98:fe:94 router REACHABLE

[ngufra]

My pf sense router shows both ipv4 and ipv6 on WAN side.

[tigertech]

My pf sense router shows both ipv4 and ipv6 on WAN side.

Does that IPv6 work when you test (say) https://test-ipv6.com ? Because now I'm getting DHCPv6 allocations of addresses on the WAN side, but they're in unroutable /64 blocks -- e.g., it gives me 2001:5a8:657:2f::2047/64, which works for pinging the Sonic router at 2001:5a8:657:2f::1, but not for global traffic. (if you "mtr 2001:5a8:657:2f::1" from outside the sonic network, it's dropped at the border.)

I'm not getting a routable DHCPv6 /56 prefix delegation like I did before this all started, so IPv6 doesn't actually work for me any more.

[bcmueller]

We just had another glitch for a short while, about 1:45pm here in Berkeley.

[ngufra]

I get 10/10 on that website.

My pf sense router shows both ipv4 and ipv6 on WAN side.

Does that IPv6 work when you test (say) https://test-ipv6.com ? Because now I'm getting DHCPv6 allocations of addresses on the WAN side, but they're in unroutable /64 blocks -- e.g., it gives me 2001:5a8:657:2f::2047/64, which works for pinging the Sonic router at 2001:5a8:657:2f::1, but not for global traffic. (if you "mtr 2001:5a8:657:2f::1" from outside the sonic network, it's dropped at the border.)

I'm not getting a routable DHCPv6 /56 prefix delegation like I did before this all started, so IPv6 doesn't actually work for me any more.