- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
I have a problem with my FIOS Internet. I have 25/25 plan however when I run ping google.com here is what I see:
Reply from 74.125.53.99: bytes=32 time=98ms TTL=49
Request timed out.
Reply from 74.125.53.99: bytes=32 time=94ms TTL=49
Reply from 74.125.53.99: bytes=32 time=94ms TTL=49
Reply from 74.125.53.99: bytes=32 time=95ms TTL=49
Reply from 74.125.53.99: bytes=32 time=92ms TTL=49
Request timed out.
Reply from 74.125.53.99: bytes=32 time=96ms TTL=49
Reply from 74.125.53.99: bytes=32 time=95ms TTL=49
Request timed out.
Request timed out.
Reply from 74.125.53.99: bytes=32 time=96ms TTL=49
Request timed out.
Reply from 74.125.53.99: bytes=32 time=91ms TTL=49
Request timed out.
The stat is - 40%-60% of my pockets are lost.
When I run ping www.yahoo.com I got 100% repsonse, but response speed is 100ms-700ms.
Now to test I go to StarBucks and using FREE 1.5 MB internet and run the same I got following:
google: 10-20ms 100%
yahoo: 14-17ms 100
I've been runing millions of tarces and in case of Yahoo I very often have dat lost between Verizon nodes:
130.81.140.114 to 130.81.10.90
In case of Google trace there issues are:
130.81.22.56 to 152.63.32.161
152.63.32.161 to 152.63.32.202
Any help will be greatly weclome.
PS. Post your tarces/pings (with locations like City, State) if you dont mind.
PSS> Few more notes.
Issue started from the day one when I was on the 15/5 plan. Verizon replaced all local equipment and cables. Now I'm on 25/25 and still the same picture.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you post up a Trace to both Yahoo! and Google for us to see? We need to see where the loss is occurring to help troubleshoot this further and how things are routing.
Starbucks most likely run on a T1. They are dated and slow for today (except on upload, where they're still awesome when comparing them to many Cable/DSL packages), but they are business class connections that often have SLAs tied to them. A side effect of this is that their routing is often loads better over residential connections.
Here's some comparative traces, which show no loss. Yeah, my latency is high, but that's because my line never gets a break and I'm on DSL.
Yahoo! (Why do I route from Buffalo to New York City to Virginia to Buffalo again?)
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\>tracert www.yahoo.com
Tracing route to any-fp3-real.wa1.b.yahoo.com [98.139.180.149]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.3.1
2 119 ms 137 ms 114 ms 10.15.3.1
3 94 ms 103 ms 103 ms so-1-1-0-0.BUFF-CORE-RTR2.verizon-gni.net [130.81.13.77]
4 81 ms 104 ms 92 ms as4-0.NY5030-BB-RTR1.verizon-gni.net [130.81.20.106]
5 94 ms 93 ms 138 ms xe-8-1-3.0.RES-BB-RTR1.verizon-gni.net [130.81.23.198]
6 70 ms 91 ms 104 ms so-6-0-0-0.ASH-PEER-RTR1-re1.verizon-gni.net [130.81.10.90]
7 93 ms 91 ms 91 ms 130.81.15.170
8 111 ms 149 ms 116 ms ae-6.pat1.dcp.yahoo.com [216.115.102.174]
9 147 ms 138 ms 150 ms ae-0.pat1.nyc.yahoo.com [216.115.101.156]
10 140 ms 126 ms 127 ms xe-1-2-0.pat1.bfy.yahoo.com [216.115.97.196]
11 157 ms 139 ms 149 ms ge-0-0-0.pat2.bfz.yahoo.com [216.115.97.209]
12 86 ms 103 ms 137 ms ae-3.msr2.bf1.yahoo.com [216.115.100.31]
13 170 ms 151 ms 137 ms et-18-25.fab1-1-gdc.bf1.yahoo.com [98.139.128.53]
14 158 ms 172 ms 128 ms po-9.bas1-7-prd.bf1.yahoo.com [98.139.129.145]
15 147 ms 126 ms 149 ms po-16.bas1-7-prd.bf1.yahoo.com [98.139.130.1]
16 192 ms 264 ms 172 ms ir1.fp.vip.bf1.yahoo.com [98.139.180.149]
Trace complete.
C:\Users\>
C:\Users\>tracert www.google.com
Tracing route to www.l.google.com [74.125.113.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.3.1
2 47 ms 57 ms 91 ms 10.15.3.1
3 92 ms 92 ms 91 ms so-1-1-0-0.BUFF-CORE-RTR1.verizon-gni.net [130.81.13.73]
4 99 ms 93 ms 103 ms as4-0.NY325-BB-RTR1.verizon-gni.net [130.81.20.104]
5 133 ms 137 ms 103 ms 0.so-4-2-0.XT1.NYC9.ALTER.NET [152.63.10.37]
6 100 ms 242 ms 137 ms 0.so-1-0-1.XT1.NYC4.ALTER.NET [152.63.0.213]
7 101 ms 103 ms 92 ms TenGigE0-4-4-0.GW8.NYC4.ALTER.NET [152.63.18.202]
8 145 ms 126 ms 126 ms google-gw.customer.alter.net [152.179.72.62]
9 69 ms 91 ms 186 ms 209.85.255.68
10 146 ms 117 ms 127 ms 209.85.251.37
11 117 ms 149 ms 116 ms 209.85.249.11
12 137 ms 152 ms 118 ms 209.85.243.114
13 143 ms 148 ms 172 ms 209.85.251.228
14 * * 133 ms 216.239.47.242
15 122 ms 103 ms 140 ms vw-in-f99.1e100.net [74.125.113.99]
Trace complete.
C:\Users\>
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is what I got for tracert yahoo.com:
Tracing route to any-fp3-real.wa1.b.yahoo.com [98.137.149.56]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 9 ms 14 ms l100.washdc-vfttp-127.verizon-gni.net [96.241.32.1]
3 6 ms 11 ms 9 ms g0-10-0-6.washdc-lcr-21.verizon-gni.net [130.81.187.12]
4 * * * Request timed out.
5 49 ms 50 ms 25 ms so-6-0-0-0.ash-peer-rtr1-re1.verizon-gni.net [130.81.10.90]
6 8 ms 10 ms 9 ms 130.81.15.174
7 13 ms 10 ms 10 ms ae-6.pat2.dce.yahoo.com [216.115.102.176]
8 59 ms 35 ms 61 ms ae-6.pat2.dax.yahoo.com [216.115.96.21]
9 97 ms 89 ms 62 ms ae-7.pat1.dax.yahoo.com [216.115.100.88]
10 100 ms 83 ms 82 ms ae-7.pat1.sjc.yahoo.com [216.115.101.149]
11 90 ms 200 ms 96 ms ae-0-d161.msr1.sp1.yahoo.com [216.115.107.59]
12 87 ms 90 ms 89 ms et-18-25.fab1-1-gdc.sp2.yahoo.com [67.195.128.67]
13 100 ms 89 ms 78 ms te-8-3.bas2-1-prd.sp2.yahoo.com [67.195.130.106]
14 100 ms 87 ms 86 ms ir1.fp.vip.sp2.yahoo.com [98.137.149.56]
Trace complete.
Will post goolg trace in few.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Google trace:
Tracing route to www.l.google.com [74.125.53.105]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 11 ms 10 ms l100.washdc-vfttp-127.verizon-gni.net [96.241.32.1]
3 12 ms 9 ms 9 ms g0-10-0-6.washdc-lcr-22.verizon-gni.net [130.81.187.10]
4 11 ms 11 ms 8 ms so-3-1-0-0.res-bb-rtr2.verizon-gni.net [130.81.151.232]
5 13 ms 16 ms 14 ms 0.so-2-0-1.xl4.iad8.alter.net [152.63.32.161]
6 22 ms 15 ms 15 ms tengige0-7-2-0.gw7.iad8.alter.net [152.63.37.94]
7 * * * Request timed out.
8 84 ms 32 ms 12 ms 72.14.238.214
9 * * 32 ms 209.85.242.208
10 * * 31 ms 72.14.237.133
11 91 ms 91 ms 89 ms 72.14.233.116
12 90 ms 97 ms * 72.14.239.12
13 96 ms 97 ms 97 ms 72.14.233.138
14 93 ms 98 ms 94 ms 64.233.174.129
15 * * 102 ms 72.14.232.6
16 96 ms * * pw-in-f105.1e100.net [74.125.53.105]
17 * * * Request timed out.
18 94 ms 95 ms 94 ms pw-in-f105.1e100.net [74.125.53.105]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Google Trace route is dropping packets it seems once it enters Google's network. The border router doesn't seem to be responding to pings so it is most likely under heavy load or not programmed to respond to them, but the packet loss from that point forward suggests a heavy load.
The trace to Yahoo! is showing high latency because you are jumping from your home to Washington DC, where you make a jump on the Yahoo! network to a location in California. That is naturally going to add some latency. Under optimimal situations, you can route from the East Coast to the West Coast within 60ms, but often times you'll find that unless you have a really high end ISP who has awesome routing to key locations and have also strategically picked Fiber routes, you'll find California from the East Coast to have 80 to 100ms of latency. What I also find interesting is that you are routing to California to reach Yahoo, where you could be sticking to the east coast like I am for my line. Probably is a DNS server case or Anycast routing taking over, but it's tough to say.
The latency is inconsistent throughout the entire trace so the problem may be anywhere. The unexplained jumps in latency I can't explain, as I don't see any obvious point that would suggest congestion is taking place. We'll need a trace during a time Google/Yahoo ping at 700ms.
Here's a trace to Google and Yahoo! from my Frontier DSL line, since I also use them as an ISP. Frontier's suffering from congestion in Rochester, NY so one past the local network in my area, speeds tank like a rock and latency shoots up.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\>tracert www.google.com
Tracing route to www.l.google.com [74.125.113.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter.westell.com [192.168.1.1]
2 16 ms 15 ms 43 ms 74-37-224-1.dsl1.hlcm.ny.frontiernet.net [74.37.224.1]
3 109 ms 108 ms 102 ms 74.40.62.37
4 104 ms 109 ms 95 ms ge-3-1--0.ar04.roch.ny.frontiernet.net [65.73.205.5]
5 89 ms 74 ms 69 ms ge--7-1-0---0.car01.roch.ny.frontiernet.net [74.45.102.5]
6 119 ms 107 ms 103 ms xe--2-2-0---0.cor01.roch.ny.frontiernet.net [74.40.5.73]
7 93 ms 98 ms 85 ms ae3---0.cor02.asbn.va.frontiernet.net [74.40.5.18]
8 96 ms 95 ms 91 ms ae0---0.cbr01.asbn.va.frontiernet.net [74.40.2.178]
9 70 ms 74 ms 77 ms 72.14.213.133
10 110 ms 107 ms 103 ms 72.14.238.214
11 117 ms 106 ms 122 ms 209.85.243.114
12 118 ms 119 ms 123 ms 64.233.174.87
13 * * * Request timed out.
14 123 ms 124 ms 127 ms vw-in-f104.1e100.net [74.125.113.104]
Trace complete.
C:\Users\>tracert www.yahoo.com
Tracing route to any-fp3-real.wa1.b.yahoo.com [98.139.180.149]
over a maximum of 30 hops:
1 <1 ms <1 ms <1ms dslrouter.westell.com [192.168.1.1]
2 17 ms 16 ms 16 ms 74-37-224-1.dsl1.hlcm.ny.frontiernet.net [74.37.224.1]
3 106 ms 101 ms 103 ms 74.40.62.37
4 78 ms 84 ms 75 ms ge-3-0--0.ar04.roch.ny.frontiernet.net [65.73.205.13]
5 107 ms 104 ms 98 ms ge--7-1-0---0.car01.roch.ny.frontiernet.net [74.45.102.5]
6 113 ms 121 ms 137 ms xe--2-2-0---0.cor01.roch.ny.frontiernet.net [74.40.5.73]
7 78 ms 73 ms 73 ms ae3---0.cor02.asbn.va.frontiernet.net [74.40.5.18]
8 128 ms 63 ms 63 ms ae0---0.cbr01.asbn.va.frontiernet.net [74.40.2.178]
9 73 ms 73 ms 68 ms g2-12-bas2.dce.yahoo.com [206.223.115.2]
10 58 ms 64 ms 79 ms ae-4.pat2.che.yahoo.com [216.115.101.145]
11 104 ms 85 ms 95 ms ae-5.pat1.bfz.yahoo.com [216.115.96.65]
12 131 ms 131 ms 134 ms ae-3.msr1.bf1.yahoo.com [216.115.100.29]
13 136 ms 137 ms 124 ms xe-5-0-0.clr2-a-gdc.bf1.yahoo.com [98.139.128.11]
14 110 ms 111 ms 129 ms xe-3-0-0.clr2-a-gdc.bf1.yahoo.com [98.139.232.99]
15 138 ms 138 ms 135 ms et-17-1.fab4-1-gdc.bf1.yahoo.com [98.139.128.43]
16 119 ms 132 ms 114 ms po-12.bas2-7-prd.bf1.yahoo.com [98.139.129.195]
17 197 ms 133 ms 127 ms ir1.fp.vip.bf1.yahoo.com [98.139.180.149]
Trace complete.
C:\Users\>
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well,
I do understand the latency jump when I go to California,
but what about jum here:
3 6 ms 11 ms 9 ms g0-10-0-6.washdc-lcr-21.verizon-gni.net [130.81.187.12]
4 * * * Request timed out.
5 49 ms 50 ms 25 ms so-6-0-0-0.ash-peer-rtr1-re1.verizon-gni.net [130.81.10.90]
It is iniside Verizon network routing from DC to PA.
Does it means that router under heavy traffic or somthing else.
I was running tracert for entire day and this jump as well as TimeOut is consistent.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@DmitryE wrote:Well,
I do understand the latency jump when I go to California,
but what about jum here:
3 6 ms 11 ms 9 ms g0-10-0-6.washdc-lcr-21.verizon-gni.net [130.81.187.12]
4 * * * Request timed out.
5 49 ms 50 ms 25 ms so-6-0-0-0.ash-peer-rtr1-re1.verizon-gni.net [130.81.10.90]It is iniside Verizon network routing from DC to PA.
Does it means that router under heavy traffic or somthing else.
I was running tracert for entire day and this jump as well as TimeOut is consistent.
That is or is not a problem. It is in fact routing from Washington DC to Ashburn, Virginia. I overlooked that jump in latency as that router could be set to de-prioritize ICMP traffic. Latency is low to the next immediate hop, which would suggest that, along with a lack of dropped packets at the next hop.
Ping that router (130.81.10.90) a few times and see if that latency remains consistently elevated, and then ping the router following that to see if latency is steady or varied like Hop 5.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well,
ping to: 130.81.187.12 goes between 7-25ms
but ping to: 130.81.10.90 goes between 40-220 ms.
I would guess it is kind of high.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
Here is trace to Verizon,NET:
Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 14 ms 5 ms 5 ms L100.WASHDC-VFTTP-127.verizon-gni.net [96.241.32.1]
3 8 ms 9 ms 11 ms G0-9-4-0.WASHDC-LCR-22.verizon-gni.net [130.81.140.154]
4 * * * Request timed out.
5 50 ms 47 ms 47 ms so-4-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81.17.41]
6 49 ms 47 ms 47 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.157]
7 49 ms 47 ms 47 ms po1.ctn-border1.vzlink.com [206.46.225.85]
8 48 ms 47 ms 47 ms po121.ctn-core1.vzlink.com [206.46.225.18]
9 48 ms 46 ms 47 ms 206.46.228.130
10 47 ms 52 ms 47 ms 206.46.232.39
Trace complete.
Two questions:
1. Request Timeout on step - Is it normal??
2. Response jump on step 5 - from 8-10 to 45-50 - And I'm still inside Verizon network. - Is it normal??
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, and yes. Number 1 means a router is simply programmed to not respond to ICMP requests. It doesn't mean that it's broken or not there. You'll find that with some core routers that push a TON of traffic, and also with a lot of government-related things as they seem to be paranoid about traceroutes.
Anyways, I would say it's a safe bet to ignore the sudden jumps in latency close to you and it is affecting other websites. ICMP Traceroute traffic is on a low priority for many core routers, so this may be what you're seeing. Latency becomes rather consistent towards the end of your last trace which means despite the jumping you're seeing initially, it's nothing that is really affecting anything. Consistent flows of data are what you're looking for, not consistent replies on ICMP traffic.