Re: [outages] [EXTERNAL] Re: ATT cellular network 2024-02-22

2024-02-22 Thread Owen DeLong via Outages
Modern phones don’t use hardware sims to the best of my knowledge, using e-sims instead. (Though I think there is still a slot for a hardware sim in case you need to work with a backwards carrier). I’ll note that this outage apparently affected ATT, Verizon, and T-Mo which account for the vast

Re: [outages] [EXTERNAL] Re: Google DNS IPv6 Prefix withdrawn?

2024-02-06 Thread Owen DeLong via Outages
Meh… I never owned the whistle, but I did teach an Atari 800 to be a blue-box/red-box/dialer back in the day. Owen > On Feb 6, 2024, at 12:08, Christopher Conley via Outages > wrote: > > Interesting way to say "I owned a Captain Crunch" whistle... :p > > -Original Message- > From:

Re: [outages] Google DNS IPv6 Prefix withdrawn?

2024-02-06 Thread Owen DeLong via Outages
D’OH!!! Well, that’ll teach me not to verify someone’s transcription error during my troubleshooting. Owen > On Feb 6, 2024, at 11:48, Warren Kumari wrote: > > Erm… > > I do not see a route to 2600:4860:4860::… > > But I *do* see routes to > The Google Public DNS IPv6 addresses are

[outages] Google DNS IPv6 Prefix withdrawn?

2024-02-06 Thread Owen DeLong via Outages
Is anyone else missing routes to 2600:4860:4860:: and ::8844? I don’t see it in my routers, nor is it visible in Route Views: route-views>sh ipv6 route 2600:4860::/32 Routing entry for ::/0 Known via "static", distance 1, metric 0 Backup from "bgp 6447 [20]" Route count is 1/1, share

Re: [outages] Optus/Akamai

2023-11-14 Thread Owen DeLong via Outages
Those are actually one and the same if you think about it, but yes, you are correct… To make matters worse, it’s not particularly deterministic which routes are dropped. However, I’ll make the argument that losing some random assortment of destinations is almost always going to be better than

Re: [outages] Netflix Currently Down

2017-10-05 Thread Owen DeLong via Outages
Additional data point: Some (significant) fraction of their staff is having some sort of gathering at the San Jose Fairmont today just down the hall from the ARIN meeting. Owen > On Oct 5, 2017, at 2:50 PM, Jason Hellenthal via Outages > wrote: > > Just a heads up to

Re: [outages] NANOG

2015-10-26 Thread Owen DeLong via Outages
> On Oct 26, 2015, at 08:41 , Joe Abley via Outages wrote: > > > > On 26 Oct 2015, at 11:26, Rich Kulawiec via Outages wrote: > >> As an aside, a couple of years ago I argued that Mailman should have >> a feature added that measured the normal rate of message flow (per

Re: [outages] Comcast San Jose,CA.

2015-05-17 Thread Owen DeLong via Outages
FWIW, I’m also in San Jose (Near Capitol x 101) and had no outage. Owen On May 15, 2015, at 18:21 , Michael Dilworth via Outages outages@outages.org wrote: Anyone have info on when I may return? ___ Outages mailing list Outages@outages.org

Re: [outages] HE IPv6 tunnel PMTU issues with juniper.net

2014-10-01 Thread Owen DeLong via Outages
This problem can be solved by setting the tcp-mss under internet-options on the juniper. I used 1280, but there may be a larger more optimal value. Owen On Oct 1, 2014, at 06:50 , Chuck Anderson via Outages outages@outages.org wrote: While on my Hurricane Electric IPv6 tunnel, I cannot

Re: [outages] HE IPv6 tunnel PMTU issues with juniper.net

2014-10-01 Thread Owen DeLong via Outages
Actually, given the nature of browsers these days, it is not at all unlikely that your request to the Juniper web server contains 1280+ octets of HTTP header data and thus is the largest packet. I think if you investigate further you will find that most flows stall at the point of a TCP packet