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 <[email protected]> wrote: > 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 2.904 ms > 2.763 ms > > 8 ae16.cr1.sjc2.us.zip.zayo.com(64.125.31.12) 3.687 ms 3.713 ms > 3.530 ms > > 9 ae27.cs1.sjc2.us.eth.zayo.com(64.125.30.230) 14.327 ms 44.579 ms > 14.265 ms > > 10 ae2.cs1.lax112.us.eth.zayo.com(64.125.28.145) 15.158 ms 14.635 ms > 15.203 ms > > 11 ae13.mpr1.lax12.us.zip.zayo.com(64.125.28.231) 20.396 ms 123.562 > ms 15.589 ms > > 12 128.177.68.30 (128.177.68.30) 13.063 ms 13.237 ms 13.228 ms > > 13 po110.bs-b.sech-lax.netarch.akamai.com (23.57.96.245) 15.009 ms > > po110.bs-a.sech-lax.netarch.akamai.com (23.57.96.243) 15.304 ms > 14.426 ms > > 14 * * * > > 15 ae120.access-a.sech-lax.netarch.akamai.com (23.57.96.249) 18.214 ms > > ae121.access-a.sech-lax.netarch.akamai.com (23.57.96.251) 17.045 ms > > ae120.access-a.sech-lax.netarch.akamai.com (23.57.96.249) 15.743 ms > > 16 * * * > > 17 * * * > > 18 * * * > > 19 * * * > > 20 * * * > > 21 * * * > > 22 * * * > > 23 * * * > > 24 * * * > > 25 * * * > > 26 * * * > > 27 * * * > > 28 * * * > > 29 * * * > > 30 * * * > > 31 * * * > > 32 * * * > > 33 * * * > > On Fri, Mar 1, 2019 at 6:38 PM James Downs <[email protected]> wrote: > >> On Mar 1, 2019, at 10:46, Luke Rockwell via Outages <[email protected]> >> 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. Going over >> Verizon LTE I can hit it >> >> >> No problems in SF from Sonic. >> >> _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages >
_______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
