Re: [outages] MIT

That looks like an akamai problem. What about a working traceroute? Does that go through the same akamai hops? On Fri, Mar 1, 2019, 9:51 PM Luke Rockwell via Outages wrote: > traceroute to w3.org (128.30.52.100), 64 hops max, 52 byte packets > > 5

Re: [outages] MIT

Trace’s from the problem locations would help someone to relay this. I can forward to a few I know. -- J. Hellenthal The fact that there's a highway to Hell but only a stairway to Heaven says a lot about anticipated traffic volume. > On Mar 1, 2019, at 20:39, Luke Rockwell via Outages >

Re: [outages] MIT

traceroute to w3.org (128.30.52.100), 64 hops max, 52 byte packets 5 ae3-124.bar2.sanfrancisco1.level3.net(4.53.130.85) 0.994 ms 1.740 ms 1.218 ms 6 ae-2-7.edge1.sanjose3.level3.net(4.69.209.169) 2.878 ms 2.699 ms 2.761 ms 7 ae6.mpr3.sjc7.us.zip.zayo.com(64.125.13.241) 2.434 ms

Re: [outages] MIT

> On Mar 1, 2019, at 10:46, Luke Rockwell via Outages > wrote: > > Anybody here know anybody at MIT? Can't access w3.org which > MIT runs or access anything other than MIT.edu my developers need to > reference W3 standards and can't. I am San Francisco going over Level3.

[outages] MIT

Anybody here know anybody at MIT? Can't access w3.org which MIT runs or access anything other than MIT.edu my developers need to reference W3 standards and can't. I am San Francisco going over Level3. Going over Verizon LTE I can hit it ___ Outages

[outages] MIT PGP keyserver down

I'm currently unable to query any keys on the keyserver which is breaking our deploys of new boxes. Anyone else seeing issues? Getting a timeout saying: Request timed during request parsing after 4 seconds Robbie Trencheny (@robbie http://twitter.com/robbie) 925-884-3728 robbie.io