- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
Driving myself crazy - could someone else please verify connectivity to www.theoatmeal.com ? I can hit it everywhere except from my home FIOS connection. Looks like a routing issue:
3 G10-0-213.CLPPVA-LCR-02.verizon-gni.net (130.81.110.174) 5.399 ms 5.414 ms 5.425 ms
4 so-12-0-0-0.RES-BB-RTR1.verizon-gni.net (130.81.28.14) 7.145 ms 7.247 ms 9.768 ms
5 0.xe-9-1-0.BR3.IAD8.ALTER.NET (152.63.39.97) 14.651 ms 14.743 ms 14.797 ms
6 ber1-ge-7-45.virginiaequinix.savvis.net (208.173.52.81) 14.893 ms 11.191 ms 13.199 ms
7 ber1-tengige-4-0-0.virginiaequinix.savvis.net (204.70.197.237) 13.293 ms 13.032 ms 13.022 ms
8 208.173.50.242 (208.173.50.242) 18.845 ms 18.888 ms 18.877 ms
9 ae2---0.cor01.asbn.va.frontiernet.net (74.40.2.173) 95.896 ms 96.000 ms 93.184 ms
10 ae1---0.cor02.chcg.il.frontiernet.net (74.40.2.193) 90.709 ms 90.623 ms 88.423 ms
11 ae0---0.cor01.chcg.il.frontiernet.net (74.40.3.241) 93.252 ms 93.404 ms 93.421 ms
12 ae1---0.cor01.lkvl.mn.frontiernet.net (74.40.5.49) 88.362 ms 91.077 ms 90.923 ms
13 ae0---0.cor01.mond.mn.frontiernet.net (74.40.5.54) 93.503 ms 92.988 ms 92.753 ms
14 xe-11-0-0--0.cor02.sttl.wa.frontiernet.net (74.40.5.46) 110.279 ms 92.199 ms 92.428 ms
15 ae0---0.cor01.sttl.wa.frontiernet.net (74.40.3.137) 90.966 ms 91.724 ms 91.697 ms
16 ae1---0.cor02.bvtn.or.frontiernet.net (74.40.1.222) 91.514 ms 91.507 ms 93.056 ms
17 74.40.1.218 (74.40.1.218) 93.368 ms 93.410 ms 93.407 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can load that site just fine via HTTP, from Boston, MA.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks. I'll ask someone else in my town to verify. Doubt Verizon will escalate if its just me 🙂
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Neighbor has the same problem.
- 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
Yeah. The IP is definitely correct ( 208.70.160.53 ).
I can't reach any of the web sites at that provider ( http://bgp.he.net/net/208.70.160.0/24#_dns )
I'll sit tight for now. Live chat had me restart my router. That's about all the help they were willing to provide for now.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1. Log into the router
2. Select My Network
3. Select Network Connections
4. Click on Broadband Connection Coax
5. Click on Settings
6. Select DHCP Release
7. Disconnect the Power for the router
8. Wait 15 minutes
9. Renew the IP Address by turning on your router.
Ideally, this should give you a new route, and if routing is the problem for you, then it should fix your issue. It sounds like routing to me.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Followed your instructions. Got a new IP address, but it is on the same /24 subnet. Same issue.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try leaving it off over night, or at least for two hours. Verizon DHCP Leases last two hours.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Definitely consider changing your IP address. You are routing properly as the route is pretty identical to me. Hits Savvis then goes to Frontier and then to the Datacenter. As you're timing out at a specific hop it could be a BOGAN filter issue if you have a newly allocated IP address range from Verizon.