- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
to add a little more information here is the trace route to www.verizon.net
Tracing route to e7327.b.akamaiedge.net [23.64.103.139]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms verizon.home [192.168.1.1]
2 8 ms 8 ms 8 ms 10.30.11.1
3 535 ms 8 ms 10 ms G2-0-3-2203.RONKVA-LCR-02.verizon-gni.net [130.81.197.2]
4 17 ms 14 ms 14 ms xe-1-0-1-0.RES-BB-RTR1.verizon-gni.net [130.81.199.48]
5 15 ms 14 ms 14 ms 0.ae4.XL2.IAD8.ALTER.NET [152.63.8.125]
6 24 ms 24 ms 52 ms 0.xe-11-2-0.GW12.IAD8.ALTER.NET [152.63.35.130]
7 23 ms 23 ms 29 ms akamai-gw.customer.alter.net [152.179.50.214]
8 24 ms 23 ms 23 ms a23-64-103-139.deploy.static.akamaitechnologies.com [23.64.103.139]
Trace complete.
which shows a pretty big different in hop delays.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ran a few more keep getting time outs at 3, either high ping, or no repsonse at all in some or all of the attempts.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
my neighbor called Earthlink, and THEY confirmed it was an outtage, and it seems to have been somewhat resolved, going to keep my eye on it.
Pretty pathetic though that another company using Verizon lines has to confirm the outtage while Verizon refuses to inform customers of outtages.