- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having some pretty consistent issues over the last couple of days with timeouts coming for certain websites (which I would imagine is a website-specific issue related to my particular IP address, like FIOS has last year or so). I'm running into a few that are happening like this:
Tracing route to cadillacforums.com [205.209.50.164]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 7 ms L100.RCMDVA-VFTTP-25.verizon-gni.net [98.117.94.1]
3 6 ms 7 ms 7 ms G12-0-4-125.RCMDVA-LCR-01.verizon-gni.net [130.81.140.116]
4 11 ms 12 ms 11 ms so-15-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.28.248]
5 13 ms 11 ms 12 ms 0.ae1.BR2.IAD8.ALTER.NET [152.63.34.21]
6 13 ms 11 ms 12 ms ae17.edge1.washingtondc12.level3.net [4.68.62.137]
7 13 ms 14 ms 14 ms vlan52.ebr2.Washington12.Level3.net [4.69.146.222]
8 31 ms 32 ms 31 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
9 32 ms 32 ms 32 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
10 61 ms 59 ms 59 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
11 231 ms 154 ms 157 ms ae-21-52.car1.Denver1.Level3.net [4.69.147.99]
12 88 ms 86 ms 87 ms DATA393-HOLDINGS.car1.Denver1.Level3.net [4.53.14.90]
13 56 ms 57 ms 57 ms 208-42-224-173.static.data393.net [208.42.224.173]
14 61 ms 59 ms 62 ms v12.colo.data393.net [208.42.224.46]
15 * * * Request timed out.
16
Solved! Go to Correct Answer
Correct answers
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So, everything just started working again suddenly.
I can reach all the sites and ping/traceroute them again.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
both of your sites work for me... but I've the problem with allthingsd.com not responding:
Tracing route to allthingsd.com [72.233.2.53]
over a maximum of 30 hops:
1 2 ms 3 ms 2 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 11 ms 12 ms L100.RCMDVA-VFTTP-24.verizon-gni.net [71.176.209.1]
3 11 ms 13 ms 12 ms G12-0-2-124.RCMDVA-LCR-01.verizon-gni.net [130.81.137.234]
4 17 ms 17 ms 16 ms so-15-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.28.248]
5 18 ms 19 ms 16 ms 0.ae1.BR2.IAD8.ALTER.NET [152.63.34.21]
6 17 ms 17 ms 14 ms ae16.edge1.washingtondc12.level3.net [4.68.62.133]
7 16 ms 17 ms 14 ms vlan51.ebr1.Washington12.Level3.net [4.69.146.190]
8 27 ms 26 ms 25 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
9 27 ms 27 ms 26 ms ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]
10 76 ms 56 ms 52 ms ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
11 * * * Request timed out.
12 * * * Request timed out.
13 53 ms 52 ms 54 ms DATABANK-HO.car2.Dallas1.Level3.net [4.71.170.2]
14 * * * Request timed out.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
oh look, we're both in Richmond, VA... guess there is still some storm or rain damage 😉
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@xrmb wrote:oh look, we're both in Richmond, VA... guess there is still some storm or rain damage 😉
Weird that it started well after the storm though, eh? They worked fine for me Friday night. Saturday, not at all.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having the same problem, mine started last week though. I can get to most sites, but some inexplicably time out. I have disabled all firewalls and antivirus and done multiple trace routes from all machines connected through my FiOS router and they all give the same results...
Tracing route to controlpanel.commandchannel.com [72.249.141.6]
over a maximum of 30 hops:
1 4 ms 1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 12 ms 8 ms L100.RCMDVA-VFTTP-18.verizon-gni.net [98.117.71.1]
3 12 ms 14 ms 11 ms G0-3-1-5.RCMDVA-LCR-21.verizon-gni.net [130.81.184.84]
4 26 ms 17 ms 14 ms so-3-3-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net[130.81.22.28]
5 13 ms 15 ms 15 ms 0.ae1.BR2.IAD8.ALTER.NET [152.63.34.21]
6 17 ms 13 ms 14 ms ae17.edge1.washingtondc12.level3.net [4.68.62.137]
7 16 ms 12 ms 12 ms vlan51.ebr1.Washington12.Level3.net [4.69.146.190]
8 27 ms 26 ms 26 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
9 26 ms 26 ms 27 ms ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]
10 55 ms 53 ms 54 ms xe-0-1-0.er2.dfw2.us.above.net [64.125.27.82]
11 * * * Request timed out.
12 121 ms 54 ms 56 ms 206.123.64.73
13 * * * Request timed out.
That's not the only site but don't have the trace route logs for others, will post later. Would love word from VZ on what exactly is going on.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Still happening here. Updated router, reset all the settings, still occuring. VZ, need some help here.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yeah I am still having the same issue. Did some more diagnostics when I got home and here are the results. Unfortunately, I don't know how to interpret them.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I play Second LIfe, and since Saturday afternoon I have been unable to log in. Also, http://www.secondlife.com is timing out.
Also, my Credit Union's online banking site which goes through lanxtraa.com is timing out.
It is definately a problem related to the FIOS network, because I am able to access the credit union's site at wok, and logged in to Second Life on a (minimal) iPad client through public wifi at a restaurant.
Oh, I'm in Richmond too.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I went thru the online chat hoops w/o success. They promised that someone at "the server team" will take a look at the issue... sure 😉
On other posts I read that renewing the IP address will fix the issue... well, I'm not in the mood trying that, because that sounds not very logical to me...