80%+ Packet Loss on a BT hop!

I've been noticing extreme lag when playing games, which seems to occur regularly every few seconds for the past few weeks, maybe months. I ran PingPlotter for a few minutes to find that one of the 'hops' is losing nearly every packet! I don't know if posting the exact IP of the hop is safe but here's a screenshot... I also noticed there's spikes coming from the homehub so that could also be the culprit... Can this be fixed on my end? Disclaimer: I don't know anything about this except from a quick google so I may be completely wrong http://i.imgur.com/dNIucdc.png

Tracing route to bbc.co.uk [212.58.246.103]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms BThomehub.home [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 44 ms 30 ms 30 ms 31.55.187.168
5 33 ms 30 ms 31 ms 195.99.127.166
6 30 ms 30 ms 31 ms 195.99.127.11
7 31 ms 30 ms 29 ms 195.99.127.7
8 29 ms 29 ms 29 ms 194.74.65.42
9 * * * Request timed out.
10 31 ms 30 ms 30 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
11 31 ms 32 ms 31 ms 132.185.255.165
12 31 ms 29 ms 30 ms fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]
Trace complete.
just ran it again and hop 9 was 241ms! that could be on bbc's side though

Similar Messages

Consistent packet loss just a few hops into Verizon's network

I have had consistent packet loss just a few hops into Verizon's network for some time. I have tried the normal things like rebooting routers and releasing my ip address but none of that helps. Most routes do not have an issue, but there is one particular service in Verizon's network which I have issues with, and it happens to be the server that Verizon routes me through when I am gaming online.
The server is : G0-3-3-6.RCMDVA-LCR-22.verizon-gni.net (130.81.191.80) and I average around 50% packet loss each night. It is just the second hop into my route:
1) My Router Internal IP
2) L100.RCMDVA-VFTTP-16.verizon-gni.net (98.117.88.1) with a ping of 9 and 0 packet loss
3) G0-3-3-6.RCMDVA-LCR-22.verizon-gni.net (130.81.191.80) with a ping of 15 and 50-80% packet loss.
How can I get Verizon to stop routing me through this troublesome server? If I look at the route to goggle.com for example, I don't go through that server and there is no packet loss at all.

mrballcb wrote:
Since it's a congested link, you also should be aware that ICMP (what ping and traceroute use) become nearly useless for determining packet loss. A router backplane assigns a grade to every packet that wants to cross from one network connection to another, and ICMP typically is assigned low grade/value. So when a router is congested and needing to drop packets, ICMP is one of the first ones to get dropped. Less than 1% of your TCP traffic may be having problems, but ICMP failure might be greater than 50%. Find a traceroute program that can use TCP to do the traceroute for more accurate results. I'm not a Windows guy, so I have no clue what programs you have which can do this.
On my Linux/Unix computer, I use tcptraceroute
On a Windows computer, you need to download and install tracetcp.
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Traceroute timeouts and lots of packet loss when a...

I host various site via the above, and since late last night and today, I am having connection timeout issues on all of them (but sites like bbc, bt etc are fine). I contacted them and performed a traceroute to my default site southee.co.uk which timed out. Below are the results:
traceroute to southee.co.uk (37.61.236.12), 64 hops max, 52 byte packets
1 bthomehub (192.168.1.254) 2.733 ms 2.414 ms 2.415 ms
2 esr5.manchester5.broadband.bt.net (217.47.67.144) 72.412 ms 29.705 ms 131.735 ms
3 217.47.67.13 (217.47.67.13) 31.390 ms 29.680 ms 103.936 ms
4 213.1.69.226 (213.1.69.226) 41.172 ms 32.700 ms 129.323 ms
5 31.55.165.103 (31.55.165.103) 30.791 ms 31.639 ms 130.306 ms
6 213.120.162.69 (213.120.162.69) 31.248 ms 59.138 ms 30.657 ms
7 31.55.165.109 (31.55.165.109) 32.159 ms 31.507 ms 31.513 ms
8 acc2-10gige-9-2-0.mr.21cn-ipp.bt.net (109.159.250.228) 31.499 ms 31.325 ms
acc2-10gige-0-2-0.mr.21cn-ipp.bt.net (109.159.250.194) 31.197 ms
9 core2-te0-12-0-1.ealing.ukcore.bt.net (109.159.250.147) 41.744 ms
core2-te0-13-0-0.ealing.ukcore.bt.net (109.159.250.139) 41.346 ms
core2-te0-5-0-1.ealing.ukcore.bt.net (109.159.250.145) 41.744 ms
10 peer1-xe3-3-1.telehouse.ukcore.bt.net (109.159.254.211) 39.527 ms
peer1-xe10-0-0.telehouse.ukcore.bt.net (109.159.254.122) 38.791 ms 38.910 ms
11 te2-3.sov-edge1.uk.timico.net (195.66.224.111) 54.032 ms 37.941 ms 38.642 ms
12 78-25-201-30.static.dsl.as8607.net (78.25.201.30) 45.830 ms 46.413 ms 42.448 ms
13 * * *
They then performed a traceroute from the server and got the following, again with timeouts and packet loss. See below:
1. 37.61.236.1 0.0% 10 0.5 0.7 0.4 2.9 0.8
2. ae0-2061.ndc-core1.uk.timico 0.0% 10 0.3 0.3 0.2 0.5 0.1
3. te2-3.sov-edge1.uk.timico.ne 0.0% 10 10.5 9.7 4.2 30.2 8.7
4. linx1.ukcore.bt.net 0.0% 10 4.1 4.3 4.1 5.9 0.6
5. host213-121-193-153.ukcore.b 0.0% 10 5.5 8.0 4.9 12.7 2.3
6. acc2-10GigE-4-3-1.mr.21cn-ip 0.0% 10 11.4 11.4 11.4 11.6 0.1
7. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8. 31.55.165.108 0.0% 10 12.1 12.1 11.8 12.4 0.2
9. 213.120.162.68 0.0% 10 12.0 12.1 12.0 12.3 0.1
10. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
I've just spent a fustrating 15 minutes with Bt Support chat who just seemed want to pass me on to the BT Business team, so I thought I'd post here, for a more informed response.

Hi Jane, Thanks for the reply. I have now purchased an AEBS(n) to try to overcome this problem. The Apple site says it is compatible with all versions of Airport card so I thought it would solve the problem. My new problem is to be found here: http://discussions.apple.com/thread.jspa?threadID=1087292&tstart=0
However to answer your questions, The OS is 10.4.10 and I have run every updater I can find for all Macs concerned. hope this helps.

Terrible Packet Loss in Game- Please help!

Computing statistics for 100 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Sam-PC.home [192.168.1.5]
0/ 25 = 0% |
1 2ms 0/ 25 = 0% 0/ 25 = 0% Wireless_Broadband_Router.home [192.168.1.1]
1/ 25 = 4% |
2 13ms 1/ 25 = 4% 0/ 25 = 0% L100.WASHDC-VFTTP-126.verizon-gni.net [173.66.228.1]
0/ 25 = 0% |
3 11ms 1/ 25 = 4% 0/ 25 = 0% G1-5-0-4.WASHDC-LCR-21.verizon-gni.net [130.81.213.68]
0/ 25 = 0% |
4 20ms 1/ 25 = 4% 0/ 25 = 0% so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.151.230]
0/ 25 = 0% |
5 12ms 1/ 25 = 4% 0/ 25 = 0% 0.xe-8-0-0.BR2.IAD8.ALTER.NET [152.63.38.129]
0/ 25 = 0% |
6 34ms 1/ 25 = 4% 0/ 25 = 0% ae17.edge1.washingtondc12.level3.net [4.68.62.137]
0/ 25 = 0% |
7 33ms 2/ 25 = 8% 1/ 25 = 4% vl-3503-ve-117.ebr1.Washington12.Level3.net [4.69.158.26]
0/ 25 = 0% |
8 29ms 3/ 25 = 12% 2/ 25 = 8% ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
0/ 25 = 0% |
9 30ms 2/ 25 = 8% 1/ 25 = 4% ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]
0/ 25 = 0% |
10 50ms 1/ 25 = 4% 0/ 25 = 0% ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
1/ 25 = 4% |
11 56ms 2/ 25 = 8% 0/ 25 = 0% ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]
0/ 25 = 0% |
12 54ms 2/ 25 = 8% 0/ 25 = 0% ae-1-60.edge2.Dallas1.Level3.net [4.69.145.11]
0/ 25 = 0% |
13 54ms 2/ 25 = 8% 0/ 25 = 0% 4.59.197.34
1/ 25 = 4% |
14 50ms 3/ 25 = 12% 0/ 25 = 0% 64.25.32.9
0/ 25 = 0% |
15 --- 25/ 25 =100% 22/ 25 = 88% 64.25.32.26
0/ 25 = 0% |
16 48ms 3/ 25 = 12% 0/ 25 = 0% 64.25.39.1
These are the results of a test I ran, but I don't know how to solve the problem. The game is unplayable because of the amount of packet loss. I know it is an issue of connection between the game and my router, so should I get a new router if mine is old?

The router I would imagine to be okay for the first bit, but for the sake of things, reboot the router and also try giving your ONT a reboot by unplugging it from AC power and then disconnecting the battery. Re-connect it after 30 seconds by connecting the battery and then plugging it back into AC power.
Also, see if the packet loss takes place during specific times of the day. If your router has a WAN connection over Coax (rather than an Ethernet connection) to your ONT, also consider checking your MoCa speeds based on this FAQ. Poor MoCa speeds can suggest shoddy coaxial causing some issues, too: https://secure.dslreports.com/faq/verizonfios/3.2_MOCA#16569
========
The first to bring me 1Gbps Fiber for $30/m wins!

Verizon FIOS Intermittent Packet Loss Problem - How to Convince Verizon Support it's NOT ME

Hi,
I have been having a problem with Verizon FIOS Internet AND Phone since Thursday afternoon.
Basically I have intermittent outages several times a day of 15-40 seconds where my download doesn't work, but upload still does. This happens on BOTH my phone and internet. Therefore it's not my router or computer equipment causing the problem.
Here's what happens:
- On the internet: I have a periodic download problem where I can receive no data for about 15 - 40 seconds. After that it returns to normal
- On the phone: If I'm on the phone at the same time then during that period of internet loss I also can not hear anything that the person I am talking to says. However they can hear me just fine (ie. download only problem)
I have been talking to Verizon technical support and they have blamed my router and ONT. I have tried switching off the router, and using a different one. Also they have replaced the ONT twice.
* This problem occurs on BOTH the phone and internet at the same time. This clearly suggests the problem is not in my own house.
In fact I know exactly where the problem lies. I did a traceroute to google below:
Tracing route to google.com [74.125.113.106]
over a maximum of 30 hops:
1     4 ms     1 ms    <1 ms 192.168.1.1
2     5 ms     4 ms     4 ms L300.NWRKNJ-VFTTP-122.verizon-gni.net [74.105.157.1]
3     9 ms     8 ms     7 ms G2-0-0-1822.NWRKNJ-LCR-08.verizon-gni.net [130.81.133.156]
4    11 ms     8 ms     7 ms P15-0.NWRKNJ-LCR-07.verizon-gni.net [130.81.30.148]
5     9 ms     6 ms     7 ms so-5-0-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.8]
6     7 ms     6 ms     7 ms 0.so-7-0-0.XL3.EWR6.ALTER.NET [152.63.19.177]
7     9 ms    10 ms     9 ms 0.so-1-0-1.XL3.NYC4.ALTER.NET [152.63.0.213]
8     9 ms     9 ms     9 ms TenGigE0-6-0-0.GW8.NYC4.ALTER.NET [152.63.22.41]
9    33 ms    31 ms    35 ms google-gw.customer.alter.net [152.179.72.62]
10     8 ms    11 ms    10 ms 209.85.252.215
11    18 ms    17 ms    16 ms 209.85.249.11
12    31 ms    29 ms    29 ms 209.85.241.222
13    30 ms    29 ms    29 ms 209.85.241.207
14    41 ms    39 ms    34 ms 209.85.243.1
15    27 ms    27 ms    29 ms vw-in-f106.1e100.net [74.125.113.106]
Trace complete.
Then I pinged each device for hops 2-4. When the problem occurs the first one in the hop - 74.105.157.1 - runs fine. The second device - 130.81.133.156 - times out, and all other devices further down the chain time out. This clearly suggest that the device:
130.81.133.156 has major problems.
I have mentioned this to tech support, but they have no way for me to send them logs. Apparently the support technicians at Verizon can not be trusted with even the most basic of tools like email and the web. They also shield me from the NT (Network technician), who is so special that even the tech support guys are only allowed to text chat with him, not actually talk to him. I have enough logs here to clearly show what the problem is.
The latest from tech support is that they are sending yet another guy by my house tomorrow to witness this problem firsthand. Then he will call support that will text chat with the NT, and MAYBE they'll start thinking it's not me.
My main question here is: "How do I get Verizon to believe it really could be a problem in their own network?"
Here are some threads from last year that explain exactly the same problem I'm having. So it wasn't just me:
http://forums.verizon.com/t5/FiOS-TV-Technical-Assistance/Verizon-FIOS-intermittent-connection-drops...
http://forums.verizon.com/t5/FiOS-Internet/Intermittent-Network-Timeouts/m-p/28138
One person said Verizon finally fixed it by replacing a PON card. I'm not sure if this is the same problem as that though.
I am an avid Starcraft player and this is driving me crazy because I am getting dropped from my games all the time. Also phone conversations suck when there's these big lags where I can't hear who I'm talking to.
I have had Verizon FIOS internet for 3 years now and this is the first problem I've ever had with it. But I'm starting to get majorly frustrated at how long it's taking to resolve the problem.
Here is a sample of the ping logs I was talking about for different devices all at the same time.
Device 2 in the Trace Route:
Reply from 74.105.157.1: bytes=32 time=78ms TTL=126
Reply from 74.105.157.1: bytes=32 time=57ms TTL=126
Reply from 74.105.157.1: bytes=32 time=41ms TTL=126
Reply from 74.105.157.1: bytes=32 time=35ms TTL=126
Reply from 74.105.157.1: bytes=32 time=34ms TTL=126
Reply from 74.105.157.1: bytes=32 time=41ms TTL=126
Reply from 74.105.157.1: bytes=32 time=43ms TTL=126
Reply from 74.105.157.1: bytes=32 time=59ms TTL=126
Reply from 74.105.157.1: bytes=32 time=24ms TTL=126
Reply from 74.105.157.1: bytes=32 time=48ms TTL=126
Reply from 74.105.157.1: bytes=32 time=5ms TTL=126
Reply from 74.105.157.1: bytes=32 time=5ms TTL=126
Reply from 74.105.157.1: bytes=32 time=5ms TTL=126
Reply from 74.105.157.1: bytes=32 time=4ms TTL=126
Reply from 74.105.157.1: bytes=32 time=3ms TTL=126
Reply from 74.105.157.1: bytes=32 time=20ms TTL=126
Reply from 74.105.157.1: bytes=32 time=19ms TTL=126
Reply from 74.105.157.1: bytes=32 time=18ms TTL=126
Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
Reply from 74.105.157.1: bytes=32 time=37ms TTL=126
Reply from 74.105.157.1: bytes=32 time=17ms TTL=126
Reply from 74.105.157.1: bytes=32 time=16ms TTL=126
Device 3 in the Trace Route:
Reply from 130.81.133.156: bytes=32 time=7ms TTL=253
Reply from 130.81.133.156: bytes=32 time=7ms TTL=253
Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
Reply from 130.81.133.156: bytes=32 time=10ms TTL=253
Reply from 130.81.133.156: bytes=32 time=9ms TTL=253
Reply from 130.81.133.156: bytes=32 time=10ms TTL=253
Reply from 130.81.133.156: bytes=32 time=13ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
Reply from 130.81.133.156: bytes=32 time=7ms TTL=253
Reply from 130.81.133.156: bytes=32 time=6ms TTL=253
Reply from 130.81.133.156: bytes=32 time=8ms TTL=253
Reply from 130.81.133.156: bytes=32 time=14ms TTL=253
Device 4 in the Trace Route:
Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
Reply from 130.81.30.148: bytes=32 time=6ms TTL=252
Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
Reply from 130.81.30.148: bytes=32 time=6ms TTL=252
Reply from 130.81.30.148: bytes=32 time=8ms TTL=252
Reply from 130.81.30.148: bytes=32 time=7ms TTL=252
Reply from 130.81.30.148: bytes=32 time=6ms TTL=252
Any help, thoughts, suggestions, etc would be great appreciated!
~David

I understand your logic, but you have not eliminated 74.105.157.1 as the problem. It could be allowing packets out, like outside callers hearing you, but not allow them back in. Since you have results pinging out, trying ping back in. Use this packet loss tool. You do not need to catch it when it's not working because this tool will ping your IP address (and all the hops in between) for up to 7 days. You will easily see when packet loss is occurring.
If it can successfully ping 74.105.157.1 when the problem occurrs, then 130.81.133.156 is not the issue. This may not help dealing with the personalities at Verizon, but it will help definitively knowing which device is the issue.

Increasing Frequency of Packet Loss

Has anyone else been experiencing packet loss more frequently in the last month? I've noticed it a few times when streaming shows or Twitch and lately it's been pretty severe when playing League of Legends.

What state are you located in? Twitch in general has been having tons of issues that they aren't owning up to. I've had a ticket open with them for a month now showing that there is a ton of issues on their end.
However, I have been having issues with packet loss in other games. Mainly with routing through the main Los Angelas Data Center. This started a month ago for me as well. I used to get a latency of 20-30 through the LA Hub. Now it spikes anywhere from 200-300ms after a certain time of day (usually 6:00PM PST). Using ping plotter, I can clearly see that the LA hub is causing most of my issues and later down the route I'm getting 10-20% packet loss in 2 other hubs before I reach the data centers for the game I'm playing.
As a gamer, you'd know the difference between 20ms and 250ms, which is what I feel after 6pm pst. Verizon Support has not owned up that it is their issue so far and the support I've reached out to from the gaming companies can clearly point out that the issue is with the Verizon data center at different hops.
I'm getting annoyed with this and it hasn't been fixed for well over a month.

Bouts of packet loss and complete loss of connection

Ok forum, I give up! I need your help.
I have an E1200 and am time out and packet loss issues. The internet connection is fine for 30 seconds to five minuets and then everything times out for 15-20 seconds. Although it’s only a minor incontinence to web browsing, it makes playing games and watching videos a nightmare. “Lost connection to server error.” and the like…
This is what I have done to remedy the problem.
I upgraded to a new router, the e1200 I am currently using, from my Tenda 10/100 N. The problems where the same that I am experience currently and the reason I bought it in the firs place.
When I directly connect to the cable modem, I have no issues and everything is fine.
I have run a trace route and the second hop, (the router to the modem) is the choke point.
I have cloned the MAC address
I have updated the firmware and hard reset
I have throttled my MTU to automatic, 1500, and 1472. None making any difference.
I have disabled NAT and all that does is kill my internet connection
I have disabled all firewalls router and windows, no change.
I replaced the physical wire from the router to the modem.
I have disconnected all devices except one computer, and no difference.
I ran a DNS trace and I have… non routable local internet address 192.168.1.1
DNS-cac-lb-01.rr.com and DNS-cac-lb-02.rr.com
I am using windows 7 and my ISP is time Warner so-cal. Help me obiwan, you’re my only hope.

Sorry friend. I have not had the gaul to load the 1.0 firmware. I am 99% sure I have the 2.0 hardware. I did however unplug my modem for an hour and then try and reconnect. The result was a lossless environment for fifteen to twenty minuets (a long time for me.). But, I am right back still having the same problem. A friend gave me a new netgear router, I am going to try that and I am going to go to Timewarner and have them replace my modem just to make sure there is nothing wrong with the surfboard. I will report back with my findings.

Tons of packet loss and Verizon techs say its fine

As you can see from the below test ran from dslreports.com, I'm having a lot of packet loss issues. This has been going on for nearly two weeks now and tech support has been more of an annoyance than a help upto this point. I've talked to tech support at least 5 times only to be told my line test comes back fine, its normal, reset your modem, delete your cookies, is your pc old, etc. I've even had them vpn itno my system and run pings and they see the packet loss and all the issues I'm having first hand and still say it isn't a big deal. On more than one occasion I've had my modem data light just flashing and had to reset the modem and they suggest I just buy a new modem. Seriously, is this how bad tech support has gotten?
I've shown them test after test after test and the all come back pretty much the same... The thing is its been perfect for years and suddenly this and its like tech support wants to sweep it under the rug or something. I've had it suggested to me the packet loss and high pings when I'm not getting the packet loss is due to my pool being over populated. Like I'm ow getting ping averages of 250-300 instead of 30-40s, again when its not all timing out.
I've posted over on the dslreports forums asking about this as well as in the Verizon specific forums to the techs all with 0 replies from anything and was told to come here and see if anyone would be able to help.
I really not bother with the hassle of switching isps as ive been a loyal Verizon dsl customer for well over 5 years but at this point just knowing how bad tech support is alone might make me want to.
Can anyone offer any insight on what else to do or help on this possibly?
Thanks.
Test Loss Min
Latency Avg
Latency Max
Latency Pass
Fail Simple ping loss check
10secs of 40byte packets 2 per second 5% loss 137ms 141ms 148ms
warn low bandwidth stream
10secs of 56k/bit ping stream 512byte packets 6% loss 142ms 147ms 154ms
warn medium bandwidth stream
10secs of 128k/bit ping stream 512byte packets 2% loss 140ms 147ms 173ms
pass your first hop ping
stream of 40byte pings to 130.81.44.101 4% loss 118ms You are 19ms
to your first hop
pass Ping plot:
Ping plot:
From East Coast - USA to YOU Hop Host LOSS Rcv Sent Best Avg Worst 0 ae-2.bb-b.slr.lxa.us.oneandone.net 0% 60 60 0.46 2.29 59.98 1 te-2-1.bb-b.ms.mkc.us.oneandone.net 0% 60 60 0.92 1.89 36.10 2 64.209.105.233 0% 60 60 13.97 41.38 948.69 3 0.xe-8-2-0.BR3.CHI13.ALTER.NET 0% 60 60 26.13 30.80 80.28 4 0.ae3.CHI01-BB-RTR1.verizon-gni.NET 0% 60 60 26.49 27.84 88.62 5 P15-3.RONKVA-LCR-01.verizon-gni.net 0% 60 60 54.25 55.01 56.32 6 P0-0.RONKVA-RONKVALK-ERXG02.verizon-gni.net 0% 60 60 116.80 121.05 130.35 7 pool-71-171-24-94.nwrknj.east.verizon.net 14% 52 60 142.49 147.61 169.10 (fail) From West Coast - USA to YOU Hop Host LOSS Rcv Sent Best Avg Worst 0 unknown.Level3.net 2% 59 60 0.64 16.67 150.86 1 ae-4-99.edge1.SanJose3.Level3.net 4% 58 60 1.15 5.12 59.35 2 4.68.63.146 0% 60 60 1.25 3.31 55.27 3 0.ae3.XL3.SJC7.ALTER.NET 0% 60 60 1.25 1.68 9.80 4 0.ge-6-3-0.XT1.DCA6.ALTER.NET 0% 60 60 75.58 77.85 108.89 5 0.so-4-0-0.RES-BB-RTR1.verizon-gni.net 0% 60 60 75.52 80.78 136.25 6 P15-3.RONKVA-LCR-01.verizon-gni.net 0% 60 60 90.25 91.97 94.08 7 P0-0.RONKVA-RONKVALK-ERXG02.verizon-gni.net 2% 59 60 154.03 159.68 164.42 8 pool-71-171-24-94.nwrknj.east.verizon.net 4% 58 60 175.74 183.27 187.00 (fail)

As you can see from the below test ran from dslreports.com, I'm having a lot of packet loss issues. This has been going on for nearly two weeks now and tech support has been more of an annoyance than a help upto this point. I've talked to tech support at least 5 times only to be told my line test comes back fine, its normal, reset your modem, delete your cookies, is your pc old, etc. I've even had them vpn itno my system and run pings and they see the packet loss and all the issues I'm having first hand and still say it isn't a big deal. On more than one occasion I've had my modem data light just flashing and had to reset the modem and they suggest I just buy a new modem. Seriously, is this how bad tech support has gotten?
I've shown them test after test after test and the all come back pretty much the same... The thing is its been perfect for years and suddenly this and its like tech support wants to sweep it under the rug or something. I've had it suggested to me the packet loss and high pings when I'm not getting the packet loss is due to my pool being over populated. Like I'm ow getting ping averages of 250-300 instead of 30-40s, again when its not all timing out.
I've posted over on the dslreports forums asking about this as well as in the Verizon specific forums to the techs all with 0 replies from anything and was told to come here and see if anyone would be able to help.
I really not bother with the hassle of switching isps as ive been a loyal Verizon dsl customer for well over 5 years but at this point just knowing how bad tech support is alone might make me want to.
Can anyone offer any insight on what else to do or help on this possibly?
Thanks.
Test Loss Min
Latency Avg
Latency Max
Latency Pass
Fail Simple ping loss check
10secs of 40byte packets 2 per second 5% loss 137ms 141ms 148ms
warn low bandwidth stream
10secs of 56k/bit ping stream 512byte packets 6% loss 142ms 147ms 154ms
warn medium bandwidth stream
10secs of 128k/bit ping stream 512byte packets 2% loss 140ms 147ms 173ms
pass your first hop ping
stream of 40byte pings to 130.81.44.101 4% loss 118ms You are 19ms
to your first hop
pass Ping plot:
Ping plot:
From East Coast - USA to YOU Hop Host LOSS Rcv Sent Best Avg Worst 0 ae-2.bb-b.slr.lxa.us.oneandone.net 0% 60 60 0.46 2.29 59.98 1 te-2-1.bb-b.ms.mkc.us.oneandone.net 0% 60 60 0.92 1.89 36.10 2 64.209.105.233 0% 60 60 13.97 41.38 948.69 3 0.xe-8-2-0.BR3.CHI13.ALTER.NET 0% 60 60 26.13 30.80 80.28 4 0.ae3.CHI01-BB-RTR1.verizon-gni.NET 0% 60 60 26.49 27.84 88.62 5 P15-3.RONKVA-LCR-01.verizon-gni.net 0% 60 60 54.25 55.01 56.32 6 P0-0.RONKVA-RONKVALK-ERXG02.verizon-gni.net 0% 60 60 116.80 121.05 130.35 7 pool-71-171-24-94.nwrknj.east.verizon.net 14% 52 60 142.49 147.61 169.10 (fail) From West Coast - USA to YOU Hop Host LOSS Rcv Sent Best Avg Worst 0 unknown.Level3.net 2% 59 60 0.64 16.67 150.86 1 ae-4-99.edge1.SanJose3.Level3.net 4% 58 60 1.15 5.12 59.35 2 4.68.63.146 0% 60 60 1.25 3.31 55.27 3 0.ae3.XL3.SJC7.ALTER.NET 0% 60 60 1.25 1.68 9.80 4 0.ge-6-3-0.XT1.DCA6.ALTER.NET 0% 60 60 75.58 77.85 108.89 5 0.so-4-0-0.RES-BB-RTR1.verizon-gni.net 0% 60 60 75.52 80.78 136.25 6 P15-3.RONKVA-LCR-01.verizon-gni.net 0% 60 60 90.25 91.97 94.08 7 P0-0.RONKVA-RONKVALK-ERXG02.verizon-gni.net 2% 59 60 154.03 159.68 164.42 8 pool-71-171-24-94.nwrknj.east.verizon.net 4% 58 60 175.74 183.27 187.00 (fail)

Packet loss when flood pinging a Mac

I had some trouble transferring large files between my iMac and my MBP the other day and so started a bit of investigation. Mistake really - here is what I found:
All mac targets are running up-to-date Leopard and use intel processors.
The home network has a linksys wireless router - all devices connected by copper.
flood ping tests with command 'sudo ping -f <target>:
from iMac to MBP shows 30% packet loss
from MBP tp iMac shows 33% packet loss
from iMac to windows laptop 0% packet loss
from iMac to linksys router 0% packet loss
from iMac to Freecom NAS box 0% packet loss
from MBP to windows laptop 0% packet loss
from MBP to linksys router 0% packet loss
from MBP to Freecom NAS box 0% packet loss
I took the macbook to work and picked targets on another site, several busy switch hops away.
from MBP to windows desktop 0% packet loss
from MBP to another iMac 26% packet loss
from MBP to mac mini 28% packet loss
from MBP to linux server 0% packet loss
from linux server to MBP 32% packet loss
The firewall is off on all the targets.
Seem clear enough - Mac machines can't handle high ping loads. It is no good telling me they don't have to. If they can answer a ping at all, they should be able to handle the load. It is a perfectly acceptable way of stress testing the link. File transfers are generally not an issue but now I want to know...
Why can't the macs handle the ping floods?
Is this indicative of any other weakness in the IP stack?
Pete

I had a suspicion of packet loss on my internet connection but could not be certain it was the ISP at fault. The fact that I had been having trouble transferring large files between my machines led me to look for possible local problems.
Network fault finding should always examine the hardware first so I wanted to see if there was anything about the cabling or the router which might be causing packet loss.
Actually copying data about the network is a pretty poor way to test things because you have several additional layer of complexity that can colour the results.
When I had narrowed down the flood ping packet loss to the macs, I went hunting on the 'net. There were plenty of people who were reporting various kinds of packet loss. Enough of them that I wondered if there was something more to it. Some of them were talking about similar symptoms to mine. The respondents usually answered a question other than the one asked so I thought I would put up some tests and see if there was actually a problem anywhere.
Now I know it is a 'feature' rather than a fault, I can work around it.
Thanks anyway
Pete

Slow and lots of packet loss

Hi Folks,
I have a wireless network set up at home with 3 macs on it. I have a G3 iMac (ruby) with an airport card (original), a Dual 1.25GHz G4 MDD also with an original airport card in it and finally a new MacBook Pro with the standard Airport Extreme 802.11N card and firmware.
Both the older machines connect and browse as one would expect them to and are lightning fast at browsing compared to the MBP. Is there some sort of mismatch with the cards?
The router is not Apple. It is a Billion 7402VGP (wireless and VoIP) with the latest firmware. It is not capable of 802.11N but is capable of 802.11g. I have tried the MBP with traceroute with 50% packet loss on wireless but none on ethernet. The G4 on wireless has no packet loss and is further away.
Any advice? What else could I tell you that would help you to help me?
MacBook Pro 15" 2.2Ghz Core 2 Duo Mac OS X (10.4.10) Wireless Card Firmware Version: 1.1.8.5

Hi Jane, Thanks for the reply. I have now purchased an AEBS(n) to try to overcome this problem. The Apple site says it is compatible with all versions of Airport card so I thought it would solve the problem. My new problem is to be found here: http://discussions.apple.com/thread.jspa?threadID=1087292&tstart=0
However to answer your questions, The OS is 10.4.10 and I have run every updater I can find for all Macs concerned. hope this helps.

Home Hub 3.0 vs Home Hub 2.0 packet loss

So I upgraded the BT package that our family is on today, and with it came the Home Hub 3.0. Happy right? Better wireless, less connection problems etc... No.
For some reason, since upgrading, I get random moments of massive packet loss. Up to 50% packets are lost for periods of up to 5 minutes. I've tried resetting the router, tried turning it off for ten minutes etc but still get regular moments of packet loss.
My internet is not interleaved at the moment so that could be a problem, however before switching to the 3.0 i never had any packet loss with non-interleaved internet (on the 2.0 homehub).
Could anyone help me?!
Thanks
Solved!
Go to Solution.

ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 03:12:19
Downstream:
7.813 Mbps
Upstream:
448 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.1 Annex A
Latency type:
Fast
Noise margin (Down/Up):
9.1 dB / 24.0 dB
Line attenuation (Down/Up):
35.5 dB / 19.5 dB
Output power (Down/Up):
19.9 dBm / 12.1 dBm
FEC Events (Down/Up):
0 / 202
CRC Events (Down/Up):
91236 / 426
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
HEC Events (Down/Up):
619777 / 655
Error Seconds (Local/Remote):
2173 / 506
est1 comprises of Best Effort Test: -provides background information.
Download Speed
4095 Kbps
0 Kbps
7150 Kbps
Max Achievable Speed
Download speedachieved during the test was - 4095 Kbps
For your connection, the acceptable range of speeds is 600-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8000 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
IP Profile for your line is - 4500 Kbps
I did a quiet line test and it sounded quiet.
Thanks for your answer, just hope someone can help me resolve it now

What can I do about Packet Loss?

Hey Verizon Community,
As the title says, what can I do about packet loss?
I have been having network spike issues in the video game Starcraft II, and Blizzard support told me to run a pathping to their servers (pathping pasted below). Upon doing that, I discovered that in hop 4, also known as G0-5-4-5.BLTMMD-LCR-22.verizon-gni.net [130.81.191.214], there was 2% packet loss. What can I do about this? Who can I contact to try and get this resolved?
PATHPING TO BLIZZARD SERVERS:
Tracing route to 12.129.202.154 over a maximum of 30 hops
0 Mitch-PC [10.0.0.2]
1 10.0.0.1
2 Wireless_Broadband_Router.home [192.168.1.1]
3 L100.BLTMMD-VFTTP-40.verizon-gni.net [96.244.79.1]
4 G0-5-4-5.BLTMMD-LCR-22.verizon-gni.net [130.81.191.214]
5 ae1-0.PHIL-BB-RTR1.verizon-gni.net [130.81.209.238]
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Mitch-PC [10.0.0.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% L100.BLTMMD-VFTTP-40.verizon-gni.net [96.244.79.1]
0/ 100 = 0% |
4 11ms 2/ 100 = 2% 2/ 100 = 2% G0-5-4-5.BLTMMD-LCR-22.verizon-gni.net [130.81.191.214]
0/ 100 = 0% |
5 23ms 0/ 100 = 0% 0/ 100 = 0% ae1-0.PHIL-BB-RTR1.verizon-gni.net [130.81.209.238]
Trace complete.

Actually it means nothing since its in the middle of the tracert. Probably the server supports the ping, but at a very low priority so the packets are being counted as lost. Many servers don't even respond to tracert.

VoIP Phones - Testing Latency, Jitter, and Packet Loss

I am having big problems with my VoIP phone connection and I'll try to lay it out clearly here.
The main telephone system resides at Location A (static IP address - see below - xxx.xxx.206.19), which has a network connection of 50MB down/20MB up (i.e., very fast). The VoIP phone configured for that system resides at Location B, which has a network connection of 10MB down/1MB up (i.e., also fast, or at least fast enough "on paper" for a quality VoIP connection). The LAN at Location A uses an Airport Extreme router, which does not have QOS or EF capability. The LAN at Location B uses a D-Link DIR-655 router which does have QOS that is configured properly to direct all traffic to the VoIP phone's IP address.
The VoIP phone at Location B is having intermittent call quality problems with skipping of words, hollowing out noises, jittery conversations, etc. All the inquiries I've made to the ISPs and phone system manufacturer (ESI) suggest that my base Internet speeds are not the problem.
I'm told, instead, that the problem might be latency, jitter, or packet loss between Location A and Location B. This leads to several questions:
(1)     Is there any Mac software that can test latency, jitter, and packet loss? I've looked at Network Utility and it seems to only measure a few things.
(2)     Does anyone see anything in the following Traceroute and Ping results (done twice from Location B to Location A) that looks problematic to VoIP quality?:
Traceroute:
First run: Traceroute has started…
traceroute to xxx.xxx.206.19 (xxx.xxx.206.19), 64 hops max, 72 byte packets
1 alfirving (192.168.0.1) 0.569 ms 0.363 ms 0.302 ms
2 10.72.28.1 (10.72.28.1) 27.567 ms 18.161 ms 22.288 ms
3 70.125.216.150 (70.125.216.150) 9.841 ms 10.346 ms 9.497 ms
4 24.164.209.116 (24.164.209.116) 11.042 ms 8.298 ms 9.433 ms
5 70.125.216.108 (70.125.216.108) 21.068 ms 20.657 ms 12.045 ms
6 te0-8-0-2.dllatxl3-cr01.texas.rr.com (72.179.205.48) 11.154 ms 11.540 ms 24.495 ms
7 107.14.17.136 (107.14.17.136) 11.994 ms 14.217 ms 15.816 ms
8 ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209) 14.566 ms 32.670 ms 15.947 ms
9 ix-0-3-2-0.tcore2.dt8-dallas.as6453.net (209.58.47.105) 11.647 ms 12.260 ms 12.386 ms
10 if-2-2.tcore1.dt8-dallas.as6453.net (66.110.56.5) 10.023 ms 12.285 ms 12.338 ms
11 209.58.47.74 (209.58.47.74) 17.641 ms 16.741 ms 16.372 ms
12 0.ae2.xl3.dfw7.alter.net (152.63.97.57) 11.584 ms 12.315 ms 12.890 ms
13 0.so-6-1-0.dfw01-bb-rtr1.verizon-gni.net (152.63.1.90) 13.812 ms
    0.ge-3-0-0.dfw01-bb-rtr1.verizon-gni.net (152.63.1.17) 18.831 ms
    130.81.23.164 (130.81.23.164) 14.189 ms
14 p14-0-0.dllstx-lcr-05.verizon-gni.net (130.81.27.40) 14.561 ms 13.621 ms 15.544 ms
15 * * *
16 static-xxx.xxx.206.19.dllstx.fios.verizon.net (xxx.xxx.206.19) 23.125 ms 24.136 ms 22.411 ms
Second run: Traceroute has started…
traceroute to xxx.xxx.206.19 (xxx.xxx.206.19), 64 hops max, 72 byte packets
1 alfirving (192.168.0.1) 0.603 ms 0.420 ms 0.324 ms
2 10.72.28.1 (10.72.28.1) 40.494 ms 26.625 ms 14.152 ms
3 70.125.216.150 (70.125.216.150) 9.431 ms 9.660 ms 9.018 ms
4 24.164.209.116 (24.164.209.116) 16.293 ms 12.339 ms 19.252 ms
5 70.125.216.108 (70.125.216.108) 15.801 ms 11.438 ms 12.068 ms
6 te0-8-0-2.dllatxl3-cr01.texas.rr.com (72.179.205.48) 23.221 ms 30.459 ms 17.519 ms
7 107.14.17.136 (107.14.17.136) 14.611 ms 15.696 ms 15.775 ms
8 ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209) 17.643 ms 14.812 ms 16.294 ms
9 ix-0-3-2-0.tcore2.dt8-dallas.as6453.net (209.58.47.105) 11.169 ms 12.374 ms 9.849 ms
10 if-2-2.tcore1.dt8-dallas.as6453.net (66.110.56.5) 16.453 ms 12.168 ms 12.384 ms
11 209.58.47.74 (209.58.47.74) 18.015 ms 14.867 ms 16.432 ms
12 0.ae2.xl3.dfw7.alter.net (152.63.97.57) 11.471 ms 11.993 ms 12.395 ms
13 0.ge-6-3-0.dfw01-bb-rtr1.verizon-gni.net (152.63.96.42) 14.077 ms 29.153 ms
    0.ge-3-0-0.dfw01-bb-rtr1.verizon-gni.net (152.63.1.17) 17.962 ms
14 p14-0-0.dllstx-lcr-05.verizon-gni.net (130.81.27.40) 14.629 ms 12.297 ms 12.839 ms
15 * * *
16 static-xxx.xxx.206.19.dllstx.fios.verizon.net (xxx.xxx.206.19) 24.976 ms 22.170 ms 22.376 ms
Ping:
First Run: Ping has started…
PING xxx.xxx.206.19 (xxx.xxx.206.19): 56 data bytes
64 bytes from xxx.xxx.206.19: icmp_seq=0 ttl=242 time=22.814 ms
64 bytes from xxx.xxx.206.19: icmp_seq=1 ttl=242 time=24.621 ms
64 bytes from xxx.xxx.206.19: icmp_seq=2 ttl=242 time=24.711 ms
64 bytes from xxx.xxx.206.19: icmp_seq=3 ttl=242 time=24.109 ms
64 bytes from xxx.xxx.206.19: icmp_seq=4 ttl=242 time=23.336 ms
64 bytes from xxx.xxx.206.19: icmp_seq=5 ttl=242 time=25.644 ms
64 bytes from xxx.xxx.206.19: icmp_seq=6 ttl=242 time=27.755 ms
64 bytes from xxx.xxx.206.19: icmp_seq=7 ttl=242 time=25.135 ms
64 bytes from xxx.xxx.206.19: icmp_seq=8 ttl=242 time=22.443 ms
64 bytes from xxx.xxx.206.19: icmp_seq=9 ttl=242 time=24.635 ms
--- xxx.xxx.206.19 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.443/24.520/27.755/1.448 ms
Second Run: Ping has started…
PING xxx.xxx.206.19 (xxx.xxx.206.19): 56 data bytes
64 bytes from xxx.xxx.206.19: icmp_seq=0 ttl=242 time=27.183 ms
64 bytes from xxx.xxx.206.19: icmp_seq=1 ttl=242 time=24.629 ms
64 bytes from xxx.xxx.206.19: icmp_seq=2 ttl=242 time=22.511 ms
64 bytes from xxx.xxx.206.19: icmp_seq=3 ttl=242 time=39.620 ms
64 bytes from xxx.xxx.206.19: icmp_seq=4 ttl=242 time=26.722 ms
64 bytes from xxx.xxx.206.19: icmp_seq=5 ttl=242 time=23.183 ms
64 bytes from xxx.xxx.206.19: icmp_seq=6 ttl=242 time=25.171 ms
64 bytes from xxx.xxx.206.19: icmp_seq=7 ttl=242 time=24.412 ms
64 bytes from xxx.xxx.206.19: icmp_seq=8 ttl=242 time=23.837 ms
64 bytes from xxx.xxx.206.19: icmp_seq=9 ttl=242 time=23.785 ms
--- xxx.xxx.206.19 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.511/26.105/39.620/4.713 ms
(3) Any other ideas on what my call quality problem might be, or how I can tweak it? For example, would putting a DIR-655 router at Location A and enabling QOS really make a difference?
Thanks to everyone, and I hope this is not too long or difficult to understand.

Hey thanks for your reply Yeah im only getting 1 ro sometimes 2 bars reception so hopefully the antenna will beef things up but I think it is what it is perhaps.

Help resolving 20-30% packet loss to many sites inc. google and youtube

I've been having issues with pages stop loading, youtube and netflix are not watchable. Netflix will buffer freeze and stop responding. Youtube will load for several seconds then stop buffering. If I refresh the page it will buffer a bit more then stop. Usually to watch a video all the way through you will have to refresh the page 4-5 times per minute of video buffered. Reading forums is also tedious as you have to constantly hit refresh to get pages to finish loading. I’ve been through the standard modem and router reboots, nothing as made a difference.
Sample ping test:
>ping -n 100 google.com
Ping statistics for 74.125.113.105:
Packets: Sent = 100, Received = 76, Lost = 24 (24% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 159ms, Average = 55ms
>ping -n 100 verizon.net
Ping statistics for 206.46.232.39:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 75ms, Maximum = 110ms, Average = 77ms
>ping -n 100 youtube.com
Ping statistics for 72.14.204.136:
Packets: Sent = 100, Received = 71, Lost = 29 (29% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 229ms, Average = 45ms
Speed tests usually report the line around 2MBit. If I connect to the VPN where I work, I do not get packet loss. The fact that the same pings through my VPN do not have the issue leads me to believe its some type of routing issue upstream from my DSLs CO.
Also is there any way I can open an online support ticket that is assigned to a Verizon resource with some chain of accountability. I'm frustrated listening to 10 minutes of automated prompts telling me to reboot the modems to get to a resource that did not understand what I meant by packet loss, then somehow disconnected to start the whole process over again.
Any assistance would be greatly appreciated. Thanks.

#1 Please post the Transceiver Status from your modem.
#2 If you don't know how to get that info:
a) What is the brand and model of your modem?
b) If you have a seperate router: What is the brand and model of it?
#3 Visit http://www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that the final hop (bottom-most line of the trace) will contain a hop with your IP address in it. Remove that line. What I'm looking for is a line that mentions "ERX" in it's name towards the end. If for some reason the trace does not complete (two lines full of Stars), keep the trace route intact.
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

90% Packet Loss while online gaming. Almost sure i...

I have been experiencing heavy packet loss for about 3 months now, hoping it would disappear at some point.
Now that I realise it won't go away, I have contacted BT and all they've done is "turn off my ping latency" which is complete bull, and refer me to the BT experts, which I'm also sure are useless.
I've been trying ping, pathping and tracert commands to the servers I connect to. Ping shows 0% packet loss, tracert has request timeouts, and pathping doesn't even go past the 1st hop.
I don't even know what to do now, this wasn't an issue before, it just popped up suddenly and I can't fix it.
After using the ping -t command to my gateway address, I am 100% sure it is a BT routing issue that needs to be fixed.

Hi neve1176,
Thanks for posting. Can you post up the results of your tracert and one from the BBC site for comparison and we'll take a look.
Cheers
David
BTCare Community Mod
If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
We are sorry but we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)

80%+ Packet Loss on a BT hop!

Similar Messages

Maybe you are looking for