Bored FiOS customers, can you post results from a ping test for me?
Not sure if this is local or what but getting a lot of dropped packets when I ping google and youtube at work. They're both around 40% fail rate. I was on the phone with my boss who was at one of our clients office and had him run the ping tests and it was dropping on him there too. I plugged my MBP directly into the FiOS ONT and was still getting dropped packets.
If I ping facebook or bing they work fine but google stuff it doesn't like. Plus I'm getting time outs when I do a tracert at hop 8 and 12.
I noticed this problem about two months ago and it's still doing it. I'm having trouble playing back 480p youtube videos on a 25mbps FiOS connection!
In order to ping on windows open a command prompt and type "ping www.google.com -n 25" without the quotes and it will send 25 ping requests.
If I ping facebook or bing they work fine but google stuff it doesn't like. Plus I'm getting time outs when I do a tracert at hop 8 and 12.
I noticed this problem about two months ago and it's still doing it. I'm having trouble playing back 480p youtube videos on a 25mbps FiOS connection!
In order to ping on windows open a command prompt and type "ping www.google.com -n 25" without the quotes and it will send 25 ping requests.
Last edited by #1 STUNNA; Sep 29, 2011 at 03:00 PM.
Not sure if this is local or what but getting a lot of dropped packets when I ping google and youtube at work. They're both around 40% fail rate. I was on the phone with my boss who was at one of our clients office and had him run the ping tests and it was dropping on him there too. I plugged my MBP directly into the FiOS ONT and was still getting dropped packets.
If I ping facebook or bing they work fine but google stuff it doesn't like. Plus I'm getting time outs when I do a tracert at hop 8 and 12.
I noticed this problem about two months ago and it's still doing it. I'm having trouble playing back 480p youtube videos on a 25mbps FiOS connection!
In order to ping on windows open a command prompt and type "ping www.google.com -t" without the quotes and it will send unlimited ping requests to cancel the pings and view the results just hit ctrl + c.
If I ping facebook or bing they work fine but google stuff it doesn't like. Plus I'm getting time outs when I do a tracert at hop 8 and 12.
I noticed this problem about two months ago and it's still doing it. I'm having trouble playing back 480p youtube videos on a 25mbps FiOS connection!
In order to ping on windows open a command prompt and type "ping www.google.com -t" without the quotes and it will send unlimited ping requests to cancel the pings and view the results just hit ctrl + c.
Reply from 74.125.159.105: bytes=32 time=43ms TTL=52
Reply from 74.125.159.105: bytes=32 time=46ms TTL=52
Reply from 74.125.159.105: bytes=32 time=45ms TTL=52
Reply from 74.125.159.105: bytes=32 time=45ms TTL=52
Ping has started…
PING www.l.google.com (74.125.226.113): 56 data bytes
64 bytes from 74.125.226.113: icmp_seq=0 ttl=55 time=9.726 ms
64 bytes from 74.125.226.113: icmp_seq=1 ttl=55 time=9.369 ms
64 bytes from 74.125.226.113: icmp_seq=2 ttl=55 time=9.045 ms
64 bytes from 74.125.226.113: icmp_seq=3 ttl=55 time=9.705 ms
64 bytes from 74.125.226.113: icmp_seq=4 ttl=55 time=9.243 ms
64 bytes from 74.125.226.113: icmp_seq=5 ttl=55 time=9.570 ms
64 bytes from 74.125.226.113: icmp_seq=6 ttl=55 time=9.079 ms
64 bytes from 74.125.226.113: icmp_seq=7 ttl=55 time=8.632 ms
64 bytes from 74.125.226.113: icmp_seq=8 ttl=55 time=8.854 ms
64 bytes from 74.125.226.113: icmp_seq=9 ttl=55 time=9.788 ms
64 bytes from 74.125.226.113: icmp_seq=10 ttl=55 time=9.284 ms
64 bytes from 74.125.226.113: icmp_seq=11 ttl=55 time=9.488 ms
64 bytes from 74.125.226.113: icmp_seq=12 ttl=55 time=9.277 ms
64 bytes from 74.125.226.113: icmp_seq=13 ttl=55 time=9.543 ms
64 bytes from 74.125.226.113: icmp_seq=14 ttl=55 time=9.055 ms
64 bytes from 74.125.226.113: icmp_seq=15 ttl=55 time=9.284 ms
64 bytes from 74.125.226.113: icmp_seq=16 ttl=55 time=9.564 ms
64 bytes from 74.125.226.113: icmp_seq=17 ttl=55 time=9.513 ms
64 bytes from 74.125.226.113: icmp_seq=18 ttl=55 time=9.065 ms
64 bytes from 74.125.226.113: icmp_seq=19 ttl=55 time=9.279 ms
64 bytes from 74.125.226.113: icmp_seq=20 ttl=55 time=8.808 ms
64 bytes from 74.125.226.113: icmp_seq=21 ttl=55 time=9.568 ms
64 bytes from 74.125.226.113: icmp_seq=22 ttl=55 time=9.826 ms
64 bytes from 74.125.226.113: icmp_seq=23 ttl=55 time=8.620 ms
64 bytes from 74.125.226.113: icmp_seq=24 ttl=55 time=8.887 ms
64 bytes from 74.125.226.113: icmp_seq=25 ttl=55 time=9.183 ms
64 bytes from 74.125.226.113: icmp_seq=26 ttl=55 time=9.016 ms
64 bytes from 74.125.226.113: icmp_seq=27 ttl=55 time=9.275 ms
64 bytes from 74.125.226.113: icmp_seq=28 ttl=55 time=9.538 ms
64 bytes from 74.125.226.113: icmp_seq=29 ttl=55 time=9.271 ms
64 bytes from 74.125.226.113: icmp_seq=30 ttl=55 time=9.075 ms
64 bytes from 74.125.226.113: icmp_seq=31 ttl=55 time=9.614 ms
PING www.l.google.com (74.125.226.113): 56 data bytes
64 bytes from 74.125.226.113: icmp_seq=0 ttl=55 time=9.726 ms
64 bytes from 74.125.226.113: icmp_seq=1 ttl=55 time=9.369 ms
64 bytes from 74.125.226.113: icmp_seq=2 ttl=55 time=9.045 ms
64 bytes from 74.125.226.113: icmp_seq=3 ttl=55 time=9.705 ms
64 bytes from 74.125.226.113: icmp_seq=4 ttl=55 time=9.243 ms
64 bytes from 74.125.226.113: icmp_seq=5 ttl=55 time=9.570 ms
64 bytes from 74.125.226.113: icmp_seq=6 ttl=55 time=9.079 ms
64 bytes from 74.125.226.113: icmp_seq=7 ttl=55 time=8.632 ms
64 bytes from 74.125.226.113: icmp_seq=8 ttl=55 time=8.854 ms
64 bytes from 74.125.226.113: icmp_seq=9 ttl=55 time=9.788 ms
64 bytes from 74.125.226.113: icmp_seq=10 ttl=55 time=9.284 ms
64 bytes from 74.125.226.113: icmp_seq=11 ttl=55 time=9.488 ms
64 bytes from 74.125.226.113: icmp_seq=12 ttl=55 time=9.277 ms
64 bytes from 74.125.226.113: icmp_seq=13 ttl=55 time=9.543 ms
64 bytes from 74.125.226.113: icmp_seq=14 ttl=55 time=9.055 ms
64 bytes from 74.125.226.113: icmp_seq=15 ttl=55 time=9.284 ms
64 bytes from 74.125.226.113: icmp_seq=16 ttl=55 time=9.564 ms
64 bytes from 74.125.226.113: icmp_seq=17 ttl=55 time=9.513 ms
64 bytes from 74.125.226.113: icmp_seq=18 ttl=55 time=9.065 ms
64 bytes from 74.125.226.113: icmp_seq=19 ttl=55 time=9.279 ms
64 bytes from 74.125.226.113: icmp_seq=20 ttl=55 time=8.808 ms
64 bytes from 74.125.226.113: icmp_seq=21 ttl=55 time=9.568 ms
64 bytes from 74.125.226.113: icmp_seq=22 ttl=55 time=9.826 ms
64 bytes from 74.125.226.113: icmp_seq=23 ttl=55 time=8.620 ms
64 bytes from 74.125.226.113: icmp_seq=24 ttl=55 time=8.887 ms
64 bytes from 74.125.226.113: icmp_seq=25 ttl=55 time=9.183 ms
64 bytes from 74.125.226.113: icmp_seq=26 ttl=55 time=9.016 ms
64 bytes from 74.125.226.113: icmp_seq=27 ttl=55 time=9.275 ms
64 bytes from 74.125.226.113: icmp_seq=28 ttl=55 time=9.538 ms
64 bytes from 74.125.226.113: icmp_seq=29 ttl=55 time=9.271 ms
64 bytes from 74.125.226.113: icmp_seq=30 ttl=55 time=9.075 ms
64 bytes from 74.125.226.113: icmp_seq=31 ttl=55 time=9.614 ms
Last edited by WILLDOGS; Sep 29, 2011 at 02:58 PM.
Ping has started…
PING www.facebook.com (69.171.229.11): 56 data bytes
64 bytes from 69.171.229.11: icmp_seq=0 ttl=240 time=100.035 ms
64 bytes from 69.171.229.11: icmp_seq=1 ttl=240 time=99.560 ms
64 bytes from 69.171.229.11: icmp_seq=2 ttl=238 time=100.535 ms
64 bytes from 69.171.229.11: icmp_seq=3 ttl=238 time=100.152 ms
64 bytes from 69.171.229.11: icmp_seq=4 ttl=240 time=100.823 ms
64 bytes from 69.171.229.11: icmp_seq=5 ttl=240 time=99.662 ms
64 bytes from 69.171.229.11: icmp_seq=6 ttl=240 time=99.930 ms
64 bytes from 69.171.229.11: icmp_seq=7 ttl=240 time=99.596 ms
64 bytes from 69.171.229.11: icmp_seq=8 ttl=240 time=99.896 ms
64 bytes from 69.171.229.11: icmp_seq=9 ttl=240 time=100.152 ms
64 bytes from 69.171.229.11: icmp_seq=10 ttl=240 time=99.675 ms
PING www.facebook.com (69.171.229.11): 56 data bytes
64 bytes from 69.171.229.11: icmp_seq=0 ttl=240 time=100.035 ms
64 bytes from 69.171.229.11: icmp_seq=1 ttl=240 time=99.560 ms
64 bytes from 69.171.229.11: icmp_seq=2 ttl=238 time=100.535 ms
64 bytes from 69.171.229.11: icmp_seq=3 ttl=238 time=100.152 ms
64 bytes from 69.171.229.11: icmp_seq=4 ttl=240 time=100.823 ms
64 bytes from 69.171.229.11: icmp_seq=5 ttl=240 time=99.662 ms
64 bytes from 69.171.229.11: icmp_seq=6 ttl=240 time=99.930 ms
64 bytes from 69.171.229.11: icmp_seq=7 ttl=240 time=99.596 ms
64 bytes from 69.171.229.11: icmp_seq=8 ttl=240 time=99.896 ms
64 bytes from 69.171.229.11: icmp_seq=9 ttl=240 time=100.152 ms
64 bytes from 69.171.229.11: icmp_seq=10 ttl=240 time=99.675 ms
Last edited by WILLDOGS; Sep 29, 2011 at 02:59 PM.
this is what I get
Pinging www.l.google.com [74.125.65.99] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 74.125.65.99: bytes=32 time=43ms TTL=251
Reply from 74.125.65.99: bytes=32 time=46ms TTL=251
Request timed out.
Reply from 74.125.65.99: bytes=32 time=43ms TTL=251
Reply from 74.125.65.99: bytes=32 time=42ms TTL=251
Request timed out.
Reply from 74.125.65.99: bytes=32 time=42ms TTL=251
Reply from 74.125.65.99: bytes=32 time=45ms TTL=251
Request timed out.
Request timed out.
Reply from 74.125.65.99: bytes=32 time=50ms TTL=251
Request timed out.
Reply from 74.125.65.99: bytes=32 time=41ms TTL=251
Reply from 74.125.65.99: bytes=32 time=42ms TTL=251
Request timed out.
Reply from 74.125.65.99: bytes=32 time=42ms TTL=251
Request timed out.
Reply from 74.125.65.99: bytes=32 time=43ms TTL=251
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.65.99: bytes=32 time=43ms TTL=251
Request timed out.
Ping statistics for 74.125.65.99:
Packets: Sent = 25, Received = 12, Lost = 13 (52% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 50ms, Average = 43ms
Request timed out.
Request timed out.
Reply from 74.125.65.99: bytes=32 time=43ms TTL=251
Reply from 74.125.65.99: bytes=32 time=46ms TTL=251
Request timed out.
Reply from 74.125.65.99: bytes=32 time=43ms TTL=251
Reply from 74.125.65.99: bytes=32 time=42ms TTL=251
Request timed out.
Reply from 74.125.65.99: bytes=32 time=42ms TTL=251
Reply from 74.125.65.99: bytes=32 time=45ms TTL=251
Request timed out.
Request timed out.
Reply from 74.125.65.99: bytes=32 time=50ms TTL=251
Request timed out.
Reply from 74.125.65.99: bytes=32 time=41ms TTL=251
Reply from 74.125.65.99: bytes=32 time=42ms TTL=251
Request timed out.
Reply from 74.125.65.99: bytes=32 time=42ms TTL=251
Request timed out.
Reply from 74.125.65.99: bytes=32 time=43ms TTL=251
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.65.99: bytes=32 time=43ms TTL=251
Request timed out.
Ping statistics for 74.125.65.99:
Packets: Sent = 25, Received = 12, Lost = 13 (52% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 50ms, Average = 43ms
Trending Topics
Code:
C:\>tracert www.google.com Tracing route to www.l.google.com [74.125.65.104] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms myrouter.home [10.20.84.1] 2 7 ms 7 ms 8 ms L100.TAMPFL-VFTTP-99.verizon-gni.net [71.122.x.x] 3 14 ms 13 ms 13 ms G0-13-4-2.TAMPFL-LCR-21.verizon-gni.net [130.81.129.60] 4 11 ms 11 ms 11 ms so-5-0-2-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net[130.81.28.212] 5 22 ms 19 ms 19 ms 0.ge-4-1-0.XL3.MIA4.ALTER.NET [152.63.4.9] 6 53 ms 53 ms 51 ms 0.xe-0-0-0.XL3.IAD8.ALTER.NET [152.63.32.214] 7 50 ms 51 ms 51 ms TenGigE0-6-1-0.GW7.IAD8.ALTER.NET [152.63.32.194] 8 51 ms 51 ms 54 ms google-gw.customer.alter.net [152.179.50.106] 9 52 ms * 52 ms 216.239.46.250 10 * 48 ms 46 ms 216.239.48.69 11 * 50 ms * 209.85.254.247 12 61 ms * * 209.85.253.214 13 * * * Request timed out. 14 * 47 ms 49 ms gx-in-f104.1e100.net [74.125.65.104] Trace complete.
The traceroute shows the issue doesn't start until after hop 8. That's well inside alter.net's network and not in Verizon's. Granted, Verizon is so big, they may have dedicated ports into alter.net where the problem is, so other ISPs might not see the problem.
From a different FIOS location:
Code:
c:\>tracert www.google.com Tracing route to www.l.google.com [74.125.73.147] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.12.50.1 2 3 ms 3 ms 3 ms l300.tampfl-vfttp-71.verizon-gni.net [173.65.x.x] 3 5 ms 4 ms 4 ms G0-5-4-4.TAMPFL-LCR-22.verizon-gni.net [130.81.110.218] 4 6 ms 4 ms 5 ms so-2-0-0-0.TPA01-BB-RTR2.verizon-gni.net [130.81.28.214] 5 11 ms 9 ms 10 ms 0.ge-3-2-0.XL4.MIA4.ALTER.NET [152.63.1.153] 6 39 ms 38 ms 40 ms 0.xe-4-1-2.XL4.IAD8.ALTER.NET [152.63.32.21] 7 40 ms 40 ms 40 ms TenGigE0-7-2-0.GW7.IAD8.ALTER.NET [152.63.37.94] 8 * * 41 ms google-gw.customer.alter.net [152.179.50.106] 9 40 ms * * 216.239.46.250 10 * * * Request timed out. 11 * * * Request timed out. 12 * 59 ms 59 ms 209.85.240.84 13 60 ms * 67 ms 216.239.46.61 14 68 ms 71 ms 70 ms 72.14.232.45 15 59 ms 59 ms 59 ms tul01m01-in-f147.1e100.net [74.125.73.147] Trace complete.
Here's what I get from the DSL location
Code:
Traceroute has started…
traceroute: Warning: www.google.com has multiple addresses; using 74.125.67.147
traceroute to www.l.google.com (74.125.67.147), 64 hops max, 72 byte packets
1 dslrouter.westell.com (192.168.1.1) 2.559 ms 1.622 ms 0.799 ms
2 l100.tampfl-dsl-13.verizon-gni.net (71.100.0.1) 26.890 ms 26.315 ms 25.985 ms
3 p0-1-1-3.tampfl-lcr-21.verizon-gni.net (130.81.34.192) 25.743 ms 25.837 ms 27.598 ms
4 so-5-0-2-0.lcc1-res-bb-rtr1-re1.verizon-gni.net (130.81.28.212) 41.491 ms 40.554 ms 35.322 ms
5 0.ge-4-1-0.xl3.mia4.alter.net (152.63.4.9) 34.025 ms 34.068 ms 32.998 ms
6 0.so-6-0-1.xl3.iad8.alter.net (152.63.0.138) 63.850 ms 64.596 ms 63.996 ms
7 tengige0-4-0-0.gw7.iad8.alter.net (152.63.37.150) 86.813 ms 64.185 ms
tengige0-6-4-0.gw7.iad8.alter.net (152.63.37.82) 65.178 ms
8 * google-gw.customer.alter.net (152.179.50.62) 64.568 ms *
9 216.239.46.250 (216.239.46.250) 64.597 ms 64.554 ms 64.470 ms
10 * 72.14.238.107 (72.14.238.107) 62.654 ms 61.496 ms
11 209.85.254.247 (209.85.254.247) 65.717 ms * *
12 64.233.174.46 (64.233.174.46) 68.891 ms * 74.196 ms
13 gw-in-f147.1e100.net (74.125.67.147) 61.776 ms 60.786 ms *
From my FIOS connection:
From my non-FIOS work connection:
Pinging google.com [72.14.204.99] with 32 bytes of data:
Reply from 72.14.204.99: bytes=32 time=11ms TTL=250
Reply from 72.14.204.99: bytes=32 time=12ms TTL=252
Request timed out.
Reply from 72.14.204.99: bytes=32 time=12ms TTL=252
Reply from 72.14.204.99: bytes=32 time=13ms TTL=250
Reply from 72.14.204.99: bytes=32 time=9ms TTL=250
Reply from 72.14.204.99: bytes=32 time=12ms TTL=250
Reply from 72.14.204.99: bytes=32 time=12ms TTL=250
Reply from 72.14.204.99: bytes=32 time=13ms TTL=252
Reply from 72.14.204.99: bytes=32 time=14ms TTL=252
Reply from 72.14.204.99: bytes=32 time=13ms TTL=252
Reply from 72.14.204.99: bytes=32 time=14ms TTL=252
Request timed out.
Reply from 72.14.204.99: bytes=32 time=13ms TTL=250
Reply from 72.14.204.99: bytes=32 time=10ms TTL=252
Request timed out.
Reply from 72.14.204.99: bytes=32 time=10ms TTL=250
Request timed out.
Reply from 72.14.204.99: bytes=32 time=13ms TTL=252
Reply from 72.14.204.99: bytes=32 time=13ms TTL=252
Request timed out.
Reply from 72.14.204.99: bytes=32 time=10ms TTL=252
Reply from 72.14.204.99: bytes=32 time=13ms TTL=252
Reply from 72.14.204.99: bytes=32 time=14ms TTL=252
Reply from 72.14.204.99: bytes=32 time=12ms TTL=252
Ping statistics for 72.14.204.99:
Packets: Sent = 25, Received = 20, Lost = 5 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 14ms, Average = 12ms
Reply from 72.14.204.99: bytes=32 time=11ms TTL=250
Reply from 72.14.204.99: bytes=32 time=12ms TTL=252
Request timed out.
Reply from 72.14.204.99: bytes=32 time=12ms TTL=252
Reply from 72.14.204.99: bytes=32 time=13ms TTL=250
Reply from 72.14.204.99: bytes=32 time=9ms TTL=250
Reply from 72.14.204.99: bytes=32 time=12ms TTL=250
Reply from 72.14.204.99: bytes=32 time=12ms TTL=250
Reply from 72.14.204.99: bytes=32 time=13ms TTL=252
Reply from 72.14.204.99: bytes=32 time=14ms TTL=252
Reply from 72.14.204.99: bytes=32 time=13ms TTL=252
Reply from 72.14.204.99: bytes=32 time=14ms TTL=252
Request timed out.
Reply from 72.14.204.99: bytes=32 time=13ms TTL=250
Reply from 72.14.204.99: bytes=32 time=10ms TTL=252
Request timed out.
Reply from 72.14.204.99: bytes=32 time=10ms TTL=250
Request timed out.
Reply from 72.14.204.99: bytes=32 time=13ms TTL=252
Reply from 72.14.204.99: bytes=32 time=13ms TTL=252
Request timed out.
Reply from 72.14.204.99: bytes=32 time=10ms TTL=252
Reply from 72.14.204.99: bytes=32 time=13ms TTL=252
Reply from 72.14.204.99: bytes=32 time=14ms TTL=252
Reply from 72.14.204.99: bytes=32 time=12ms TTL=252
Ping statistics for 72.14.204.99:
Packets: Sent = 25, Received = 20, Lost = 5 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 14ms, Average = 12ms
From my non-FIOS work connection:
Pinging google.com [72.14.204.99] with 32 bytes of data:
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Reply from 72.14.204.99: bytes=32 time=10ms TTL=54
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Reply from 72.14.204.99: bytes=32 time=14ms TTL=54
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Reply from 72.14.204.99: bytes=32 time=10ms TTL=54
Reply from 72.14.204.99: bytes=32 time=13ms TTL=54
Reply from 72.14.204.99: bytes=32 time=37ms TTL=54
Reply from 72.14.204.99: bytes=32 time=42ms TTL=54
Reply from 72.14.204.99: bytes=32 time=41ms TTL=54
Reply from 72.14.204.99: bytes=32 time=38ms TTL=54
Reply from 72.14.204.99: bytes=32 time=38ms TTL=54
Reply from 72.14.204.99: bytes=32 time=50ms TTL=54
Reply from 72.14.204.99: bytes=32 time=35ms TTL=54
Reply from 72.14.204.99: bytes=32 time=35ms TTL=54
Reply from 72.14.204.99: bytes=32 time=38ms TTL=54
Reply from 72.14.204.99: bytes=32 time=46ms TTL=54
Reply from 72.14.204.99: bytes=32 time=36ms TTL=54
Reply from 72.14.204.99: bytes=32 time=41ms TTL=54
Reply from 72.14.204.99: bytes=32 time=10ms TTL=54
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Reply from 72.14.204.99: bytes=32 time=10ms TTL=54
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Ping statistics for 72.14.204.99:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 50ms, Average = 24ms
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Reply from 72.14.204.99: bytes=32 time=10ms TTL=54
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Reply from 72.14.204.99: bytes=32 time=14ms TTL=54
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Reply from 72.14.204.99: bytes=32 time=10ms TTL=54
Reply from 72.14.204.99: bytes=32 time=13ms TTL=54
Reply from 72.14.204.99: bytes=32 time=37ms TTL=54
Reply from 72.14.204.99: bytes=32 time=42ms TTL=54
Reply from 72.14.204.99: bytes=32 time=41ms TTL=54
Reply from 72.14.204.99: bytes=32 time=38ms TTL=54
Reply from 72.14.204.99: bytes=32 time=38ms TTL=54
Reply from 72.14.204.99: bytes=32 time=50ms TTL=54
Reply from 72.14.204.99: bytes=32 time=35ms TTL=54
Reply from 72.14.204.99: bytes=32 time=35ms TTL=54
Reply from 72.14.204.99: bytes=32 time=38ms TTL=54
Reply from 72.14.204.99: bytes=32 time=46ms TTL=54
Reply from 72.14.204.99: bytes=32 time=36ms TTL=54
Reply from 72.14.204.99: bytes=32 time=41ms TTL=54
Reply from 72.14.204.99: bytes=32 time=10ms TTL=54
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Reply from 72.14.204.99: bytes=32 time=10ms TTL=54
Reply from 72.14.204.99: bytes=32 time=11ms TTL=54
Ping statistics for 72.14.204.99:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 50ms, Average = 24ms
I was at my friends house yesterday who I know has FiOS so I ran a tracert and same thing, it starts dropping packets after hop 8.
M06V0.png
Why? Is this intentional? Once I thought about it I remember being at their house months ago probably after I got my iPad 2 and youtube sucking over there. I asked them if they've always had issues with youtube videos loading slow and they said yes. So this has been going on for a while. Verizon must know about it so I don't know what good notifying them would do.
M06V0.png
Why? Is this intentional? Once I thought about it I remember being at their house months ago probably after I got my iPad 2 and youtube sucking over there. I asked them if they've always had issues with youtube videos loading slow and they said yes. So this has been going on for a while. Verizon must know about it so I don't know what good notifying them would do.
Thread
Thread Starter
Forum
Replies
Last Post
urbtsx
1G TSX Performance Parts & Modifications
9
Mar 4, 2017 06:53 PM
Yumcha
Automotive News
4
Sep 13, 2015 01:59 PM













