DATA PACKET LOSS! Websites SLOW!

I have tested on 3 different computers on my network.. and I went to my parents house who also have FIOS and the websites that I frequent are slow.. VERY SLOW.. My dedicated servrer hosted at Hostgator is VERY SLOW. and It is VERY rubust.. I Then went to a friends house who has comcast and everything worked FINE!
The datacenter that runs my server track down the problem and said that Verizon FIOS right now is loosing alot of data packets. How can we get this fixed?? I hate to call customer service because they refuse to talk to anyone like they are not a 90 year of lady with no tech experience.
VERIZON PLEASE TRACK DOWN THE PROBLEM ON YOUR END! This is unacceptable!

This is a peer-to-peer support forum. If you want to get a message to Verizon, you should contact them directly via one of the options on their Contact Us page.
If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer as Accepted Solution so others can see the solution to the problem.
"All knowledge is worth having."

Similar Messages

Monitoring RTP Data / Packet Loss / Packet Delay

hiya folks
what is everyone using to monitor their incoming and outgoing data in terms of packet delay and loss and myabe even load on the CPU??
thanking anyone in advance for any help you provide

i managed to do this now without the use of an external program, once you have finished transmitting the stream.
you can run the following bit of code on thr rtp manager which shows you the following
GlobalTransmissionStats stats;
for (int i = 0; i < rtpMgrs.length; i++) {
stats = rtpMgrs.getGlobalTransmissionStats ();
System.out.println( "The total number of RTP packets transmitted :" + stats.getRTPSent() );
System.out.println( "The total number of bytes sent :" + stats.getBytesSent() );
System.out.println( "The total number of RTCP packets sent :" + stats.getRTCPSent() );
System.out.println( "The total number of local collisions :" + stats.getLocalColls() );
System.out.println( "The total number of remote collisions :" + stats.getRemoteColls() );
System.out.println( "The number of packets that failed to get transmitted :" + stats.getTransmitFailed() );
rtpMgrs[i].removeTargets( "Session ended.");
rtpMgrs[i].dispose();

Extremely slow internet and 20-50% packet loss

This has been happening for at least a week. I've been trying to play online games such as dota 2 where I have up to 50% packet loss at times. I also try to watch streams however it is usually constantly buffering every 5 seconds on any quality over 240p. I have tried restarting both my modem and router. I've also done a ping test to google which came back with:Pinging google.com [216.58.216.110] with 32 bytes o
Reply from 216.58.216.110: bytes=32 time=12ms TTL=5
Reply from 216.58.216.110: bytes=32 time=11ms TTL=5
Reply from 216.58.216.110: bytes=32 time=11ms TTL=5
Reply from 216.58.216.110: bytes=32 time=12ms TTL=5
Ping statistics for 216.58.216.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11msSometimes I will have no packet loss as shown but other times I will have 50%. It happens randomly. However streams will never work above 240p. I have tried speedtesting my internet when it is slow and it comes back the usual 20 Mbps down and 5 up. Anyone know whats going on or any tests I can try? It is extemely frustrating not knowing what to do

mattsmith927 wrote:
This has been happening for at least a week. I've been trying to play online games such as dota 2 where I have up to 50% packet loss at times. I also try to watch streams however it is usually constantly buffering every 5 seconds on any quality over 240p. I have tried restarting both my modem and router. I've also done a ping test to google which came back with:
Pinging google.com [216.58.216.110] with 32 bytes o
Reply from 216.58.216.110: bytes=32 time=12ms TTL=5
Reply from 216.58.216.110: bytes=32 time=11ms TTL=5
Reply from 216.58.216.110: bytes=32 time=11ms TTL=5
Reply from 216.58.216.110: bytes=32 time=12ms TTL=5
Ping statistics for 216.58.216.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms
Sometimes I will have no packet loss as shown but other times I will have 50%. It happens randomly. However streams will never work above 240p. I have tried speedtesting my internet when it is slow and it comes back the usual 20 Mbps down and 5 up.
Anyone know whats going on or any tests I can try? It is extemely frustrating not knowing what to do
I am sorry to hear about the trouble you are having with this. Has this happened recently? I was able to check the connection history and it does seem to be much better for the past week. If the issue comes back let me know, we might need to have a tech check this. -FC

High Packet Loss, High Ping and Slow Connection Ov...

Hi There,
I have been a customer with the BT unlimited broadband package for a little under two years and up until recently have had no real issues with the service. This was until around 3/4 weeks ago I noticed that the internet was very slow and certain online games or applications like Netflix would lose all of its quality or stop completely. At first I thought nothing of it and simply reset my BT Home hub router, and sure enough everything was back to normal. However after around 2-3 hours of moderate use (gaming online or watching Netflix) the problem surfaced again.
Now I am lucky if I can get the entire way through a 40 minute TV episode before the quality drops and/or the service requires buffering. I have already contacted BT via the helpline and the service lady ran through the obligatory steps (turn off, wait 5 minutes, reset the home hub etc.) but she failed to understand that although rebooting the home hub does alleviate the problem initially, the symptoms of a slow connection, high packet loss and high ping always return within an hour.
Four the last couple of weeks I have been trying to investigate the problem myself and I have done the following things:
Tested the line using the master socket (no difference)
Opened the ports on my firewall within the home hub (no difference)
Directly wired in the computer instead of relying on the wifi (no difference)
Tested for interference from neighbours wifi using inSSIDider office (it wasn’t, operating on different channels)
Switched every device that requires internet off apart from the PC (no difference)
So with all that in mind I am fairly confident that it is nothing within my house that has caused a significant reduction in internet quality.
Now I have tried my best to display the problem I am having by recording the connection quality for the last 24 hours. The table below represents the condition and quality of the connection after leaving it a period of time without resetting:
ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 21:52:14
Downstream:
12.96 Mbps
Upstream:
910 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
6.7 dB / 5.4 dB
Line attenuation (Down/Up):
29.4 dB / 16.4 dB
Output power (Down/Up):
20.4 dBm / 12.6 dBm
FEC Events (Down/Up):
987297 / 12745
CRC Events (Down/Up):
254 / 15268
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):
2437 / 252630
Error Seconds (Local/Remote):
189 / 36430
And here is a result of the ping and packet loss during this time:
Now I immediately reset the home hub after running that test and ran the test again. These are the results I a achieved within 2 minutes of internet connectivity:
ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 00:01:05
Downstream:
13.77 Mbps
Upstream:
910 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
6.4 dB / 5.6 dB
Line attenuation (Down/Up):
29.4 dB / 16.4 dB
Output power (Down/Up):
20.4 dBm / 12.6 dBm
FEC Events (Down/Up):
159 / 12746
CRC Events (Down/Up):
1 / 15573
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):
0 / 252639
Error Seconds (Local/Remote):
1 / 36438
Even within the time it has taken to compose this page my internet quality has nose-dived from the previous result above to the following:
Connection Information
Line state:
Connected
Connection time:
0 days, 00:52:31
Downstream:
13.77 Mbps
Upstream:
910 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
6.1 dB / 5.4 dB
Line attenuation (Down/Up):
29.4 dB / 16.4 dB
Output power (Down/Up):
20.4 dBm / 12.6 dBm
FEC Events (Down/Up):
14544 / 12749
CRC Events (Down/Up):
14 / 15584
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):
72 / 252647
Error Seconds (Local/Remote):
10 / 36449
What is causing this poor quality in connection and what can be done to rectify the problem?
Thank you for your response in advanced.
Regards,
Richard.

Thank you for you quick reply, I have just moved my hub to the master socket again and re-run the test and I seem to be getting the same results.
ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 00:17:47
Downstream:
12.96 Mbps
Upstream:
910 Kbps
ADSL Settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
6.0 dB / 5.2 dB
Line attenuation (Down/Up):
28.7 dB / 15.9 dB
Output power (Down/Up):
20.4 dBm / 12.6 dBm
FEC Events (Down/Up):
26417 / 5
CRC Events (Down/Up):
1 / 303
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):
31 / 11
Error Seconds (Local/Remote):
10 / 36522
I have also checked if the bell wire was attached and it is not. My socket is of the new type with the inclusion of an inductor on the faceplate. My ADSL filters and modem cable already have the middle connecting pins removed so I don’t think it is a wiring problem, at least in my apartment anyway. I have also searched for problems with the exchange and they are showing green for my area. (Liverpool Central)
I have just rang the quiet line and I do not appear to have any noise on the line. However, all I have is a cordless phone and I know that is not ideal for determining noise due to the radio frequency interfering with the phone speaker.
Again thank you for you time on this issue.
Regards,
Richard

Verizon Fios & NTT Packet loss/Slow Speeds..

Hello,
Recently there has been lot of packet loss between NTT and Verizon Fios.
mtr -rn 108.51.80.12x
HOST: localhost Loss% Snt Last Avg Best Wrst StDev
1.|-- 77.247.178.xxx 0.0% 10 0.4 0.4 0.3 1.2 0.3
2.|-- 85.159.239.6 0.0% 10 0.5 0.5 0.4 0.5 0.0
3.|-- 85.159.239.29 0.0% 10 0.9 0.9 0.6 2.4 0.5
4.|-- 81.20.64.113 0.0% 10 1.2 1.1 1.0 1.2 0.1
5.|-- 129.250.2.146 0.0% 10 1.3 1.3 0.8 3.9 1.0
6.|-- 129.250.2.144 0.0% 10 96.0 97.5 96.0 108.8 4.0
7.|-- 129.250.4.207 0.0% 10 92.6 92.7 92.5 93.0 0.1
8.|-- 129.250.8.38 0.0% 10 144.8 148.0 142.2 164.0 7.1
| `|-- 129.250.8.34
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- 108.51.80.12x 10.0% 10 142.5 143.9 141.2 146.7 2.2
Anyone else having same issues? I tried contacting support but problem happens offten at night time and is fixed within 6 to 8 hours.
Thanks

Hi, wondering if you were ever able to resolve this or get any additional info from Verizon on it?
I have some customers on FIOS reporting problems to our ec2 servers. After some a couple nights of debugging I found your post and I have a set of remarkably similar mtr output (also have a similar trace to a 108.x.x.x FIOS endpoint):
HOST: ip-10-45-5-2xx Loss% Snt Last Avg Best Wrst StDev
1.|-- 100.104.104.1xx 0.0% 10 0.7 1.3 0.7 6.3 1.8
2.|-- 100.74.169.9 0.0% 10 0.4 0.5 0.4 0.7 0.1
3.|-- 100.74.169.24 0.0% 10 0.4 0.5 0.4 0.6 0.1
4.|-- 100.66.98.4 0.0% 10 0.4 0.4 0.3 0.5 0.0
5.|-- 100.66.3.190 0.0% 10 1.3 1.3 0.9 1.7 0.2
6.|-- 100.64.226.55 0.0% 10 1.0 1.4 0.9 2.2 0.4
7.|-- 100.64.225.182 0.0% 10 1.5 1.3 0.9 2.6 0.5
8.|-- 100.64.58.100 0.0% 10 0.4 1.2 0.3 5.6 1.8
9.|-- 100.64.13.89 0.0% 10 1.0 1.3 0.9 2.3 0.4
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- 100.64.16.1 0.0% 10 0.5 1.4 0.4 7.6 2.2
14.|-- 205.251.245.43 0.0% 10 6.6 9.8 0.4 66.4 20.4
15.|-- 205.251.245.46 0.0% 10 0.7 0.9 0.7 1.1 0.1
16.|-- 205.251.245.0 0.0% 10 1.2 1.1 0.8 1.2 0.1
17.|-- 168.143.228.37 0.0% 10 1.4 1.4 1.4 1.5 0.0
18.|-- 129.250.8.38 0.0% 10 46.4 49.8 46.4 52.6 2.2
| `|-- 129.250.8.34
19.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
20.|-- 173.79.220.xxx 10.0% 10 63.1 59.8 53.7 63.1 2.9
Wondering how to proceed with Verizon, as you mention this only seems to occur during night-time hours, so it's a tricky issue to get support on. For us it means very slow (1mbps or less) transfer speeds between our servers and the FIOS customer, which is unacceptable.
-Tom

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.

Very slow upload speeds and packet loss

I have the exact same issue as the following threads.
https://community.bt.com/t5/BT-Infinity-Speed-Connection/Very-bad-connection-Packet-Loss-very-low-up...
https://community.bt.com/t5/BT-Infinity-Speed-Connection/extremely-low-upload-speeds-and-high-latenc...
My download speed is around 36M and my upload speed on speed tests either fails to connect or I get around 0.5M. Pinging google leads to frequent none responses, probably on average 1 in ever 8 pings fails.
I have rebooted the router, reset the router to factory settings and disconnected all devices apart from 1 clean CentOS desktop pc to do the speed test and still get the same results. Could someone please give me details so I can get this investigated properly and soon as it is effecting my work.

Still experiencing unusable upload speeds, can someone please help me with this? Below is todays test.
FAQ
1. Best Effort Test: -provides background information.
Download Speed
37.88 Mbps
0 Mbps
38.71 Mbps
Max Achievable Speed
Download speedachieved during the test was - 37.88 Mbps
For your connection, the acceptable range of speedsis 20 Mbps-38.71 Mbps .
Additional Information:
IP Profile for your line is - 38.71 Mbps
2. Upstream Test: -provides background information.
Upload Speed
0.31 Mbps
0 Mbps
10 Mbps
Max Achievable Speed
Upload speed achieved during the test was - 0.31Mbps
Additional Information:
Upstream Rate IP profile on your line is - 10 Mbps

Major Packet Loss

Who else is getting major packet loss to various US websites including twitter.com?
Here's my ping log:
ping twitter.com /t
Pinging twitter.com [199.59.150.39] with 32 bytes of data
Request timed out.
Request timed out.
Reply from 199.59.150.39: bytes=32 time=172ms TTL=236
Reply from 199.59.150.39: bytes=32 time=158ms TTL=236
Request timed out.
Request timed out.
... (and so on)
Ping statistics for 199.59.150.39:
Packets: Sent = 84, Received = 32, Lost = 52 (61% loss),
Approximate round trip times in milli-seconds:
Minimum = 158ms, Maximum = 230ms, Average = 168ms
The 61% packet loss is causing the Internet to slow down to a crawl...
I have pinged from an external machine and all seems fine there, what is going on?
This is on BT Infinity.

Hi,
Yes I'm experiencing the same thing and it's very annoying as several of the servers I host out there are affected - one of which is a streaming service which BT is currently making look really awful.
The problem lies with BTs peering with above.net in London. Here is an MTR trace to one of the IP addresses:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| FTTC-BT - 0 | 453 | 453 | 0 | 0 | 0 | 0 |
| 217.32.143.131 - 0 | 453 | 453 | 12 | 12 | 13 | 12 |
| 217.32.143.158 - 0 | 453 | 453 | 12 | 16 | 177 | 111 |
| 213.120.181.238 - 0 | 453 | 453 | 12 | 12 | 13 | 13 |
| 217.41.169.73 - 0 | 453 | 453 | 12 | 12 | 15 | 13 |
| 217.41.169.107 - 0 | 453 | 453 | 12 | 13 | 15 | 13 |
| acc1-10GigE-9-2-0.sf.21cn-ipp.bt.net - 0 | 453 | 453 | 12 | 14 | 82 | 12 |
| core1-te0-2-3-0.ealing.ukcore.bt.net - 0 | 453 | 453 | 17 | 22 | 140 | 26 |
| peer1-xe0-1-0.redbus.ukcore.bt.net - 0 | 453 | 453 | 19 | 22 | 80 | 20 |
| ge-2-1-0.mpr1.lhr2.uk.above.net - 40 | 177 | 107 | 18 | 26 | 143 | 21 |
| ge-4-1-0.mpr1.lhr2.uk.above.net - 39 | 178 | 109 | 19 | 22 | 91 | 19 |
| xe-5-2-0.cr1.dca2.us.above.net - 35 | 192 | 126 | 92 | 95 | 146 | 129 |
| xe-2-2-0.cr1.iah1.us.above.net - 41 | 173 | 103 | 118 | 123 | 173 | 120 |
| xe-1-2-0.cr1.dfw2.us.above.net - 36 | 189 | 122 | 122 | 128 | 183 | 126 |
| xe-0-0-0.er3.dfw2.us.above.net - 36 | 189 | 122 | 125 | 131 | 201 | 163 |
| 64.124.193.221.t01263-01.above.net - 39 | 178 | 109 | 123 | 131 | 198 | 124 |
| xe-5-3-0.core4.dllstx01.corexchange.com - 38 | 182 | 114 | 124 | 132 | 234 | 124 |
| premium-network.incero.com - 37 | 186 | 119 | 122 | 125 | 155 | 123 |
| cg.incero.com - 33 | 197 | 132 | 123 | 125 | 190 | 129 |
| 23.29.127.154 - 31 | 205 | 142 | 124 | 126 | 154 | 129 |
| 108.166.187.35 - 37 | 185 | 117 | 124 | 126 | 194 | 124 |
|________________________________________________|______|______|______|______|______|______|
Sort it out BT!

Help- WDS with Extreme-N & 2x Airport Express with ~ 40% packet loss

So this problem is driving me crazy. I recently moved into a house that has enough metal in the walls (don't ask) to prevent me from using a single base station so I expanded my network as a WDS utilizing an Airport Extreme (mixed NGB mode) and two Airport Express (one as a relay and one as remote). The configuration appears to work normally some times but other times (especially evenings) I get a very high rate of dropped packets between the client notes (which are connected through the WDS-enabled Expresses) and the base station (using a simple ping 10.0.1.1 to check connectivity to the APBS-N). The problem manifests itself from a users' perspective as very long DNS lookups which causes slow page loads in a browser but it's very reproducible via ping.
So far I've tried changing the channels on the network but I haven't seen a huge payoff there. iStumbler reports no additional networks on channel 2 which I'm using, there are some on channel 1, 5, and 13. I've also tried channels 7 and 11. We have no microwave in the house and our cordless phone (5.8ghz) never interrupted with our simpler Express-based network at our old house, n/m the fact that the phone is never in use when we have this problem.
I don't seem to see the problem when I'm local to (in the same room as) the AEBS; it really seems to happen only when I'm on the WDS-enabled remote and/or relay.
Other data points that may help are that the AEBS-N drops out of the Airport utility at the same time. Sometimes isn't gone for 30 seconds, other times for > 30 minutes. The other base stations continue to report "Green" in that they are not having any WDS problems. If I disconnect the remote node the relay will correctly reflect a status of yellow, so I know it somewhat works.
It's an open network (no encryption, open SSID) so it's unlikely that there's an issue there.
Clients include an Apple TV, iBook G4, MacBook, Tivo Series 3, Intel Mini and Dell Latitude D810. Because of the diversity of clients I don't think it's a driver or NIC adapter issue on any of the clients.
Does anyone have any experience working in a similar environment? Suggestions on troubleshooting packet loss (or other performance issues) in a WDS network?
Thanks,
Mike

Hello errorsupply. Welcome to the Apple Discussions!
I suggest downloading a copy of iStumbler. Use iStumbler's Inspector feature (select Edit > Inspector from iStumbler's menu) to determine the Signal-to-Noise Ratio (SNR) at different points around your house, by performing a simple RF site survey. Within the Inspector, note the values for "signal" & "noise" at these locations. Start with your MacBook near the main base station, note the readings, and then, choose the locations where you have the relay and remote base stations.
SNR is the signal level (in dBm) minus the noise level (in dBm). For example, a signal level of -53dBm measured near an access point and typical noise level of -90dBm yields a SNR of 37dB, a healthy value for wireless LANs.
The SNR, as measured from the MacBook, decreases as the range to the base station increases because of applicable free space loss. Also an increase in RF interference from microwave ovens and cordless phones, which increases the noise level, also decreases SNR.
SNR Guideline
o 40dB+ SNR = Excellent signal
o 25dB to 40dB SNR = Very good signal
o 15dB to 25dB SNR = Low signal
o 10dB to 15dB SNR = Very low signal
o 5dB to 10dB SNR = No signal
If the SNR is 20dB+ at each of these locations, then you should be getting reasonable performance from your AirPorts. If less, either try to locate/eliminate the source of the Wi-Fi interference or try relocating the relay and/or remote base station until they are within a 20dB SNR range of the main (and for the remote, of the relay).

Flood ping of loopback device gives 20% packet loss!

While trying to diagnose a problem with my Airport Express (high packet loss even with a strong signal), I noticed that my Macbook cannot reliably flood ping its own loopback device!
bash-3.2$ $ sudo ping -f 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 56 data bytes
....^C
--- 127.0.0.1 ping statistics ---
994 packets transmitted, 750 packets received, 24% packet loss
round-trip min/avg/max/stddev = 0.012/0.017/0.103/0.007 ms
As the loopback interface is internal, I get precisely the same result whether Airport is turned on or off.
This seems completely crazy to me! Anyone have any idea what might be going on?
Message was edited by: zzz Matt Taylor (replaced ping output with one with linebreaks to avoid excessively wide post)

Can't help you specifically with that, but just last night my Atheros AR5008 adapter starting dropping 40%-80% of the packets to my router. It's unusably slow now. I had this problem with the 2.6.38 kernel and was able to solve it by passing the nohwcrypt option to the ath9k module, but that doesn't work anymore.
I'm now on the 3.0.4 kernel, Arch x64. Last updates that MAY be relevant were dbus-sharp, dbus-sharp-glib, and gnutls. I started having problems the day after upgrading these packages. I'm connecting in 802.11n mode.
I've been looking for evidence of related bugs but so far nothing. I wonder if this is a broader issue affecting more than just the Atheros or Ralink drivers?
EDIT: downgrading gnutls from 3.0.3-1 to 3.0.2-1 reduced my packet loss to about 15%, so the internet is now basically usable. I also tried downgrading glib-networking (which I updated to version 2.28.7-5 a few days back), but that didn't seem to help.
Last edited by rsking84 (2011-09-22 01:32:59)

Excessive Packet Loss 1.87 Mb/s Down 39.63 Mb/s Up - 90.19% limited?

Hello everyone, my name is Sherri. I became a Fios Internet 50/25 subscriber 4 days ago. For the first 24 hours speedtest.verizon.net was giving me as much as a 60/30 speed results. The next morning I noticed web pages taking abnormally long to load (even google.com), so I decided to check my speed again and am now getting as low as 1MB/s download wired or wirelessly. My upload remains unaffected but browsing can get so slow it's almost unusable. Any large downloads I try end up failing (i.e. cyanogenmod nightlies). This has been going on for the past 3 days on all of my devices (android, PC, Macbook).
How can I check if this is a fixable problem on my end or if it's a problem with Fios in my area that I just need to wait out? I called tech support and they just want to send me a new router, but if it was the router wouldn't my upload be affected as well?
Network diagnostic tool:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [131768]
running 10s outbound test (client to server) . . . . . 39.63Mb/s
running 10s inbound test (server to client) . . . . . . 1.87Mb/s
------ Client System Details ------
OS data&colon; Name = Mac OS X, Architecture = x86_64, Version = 10.8.4
Java data&colon; Vendor = Oracle Corporation, Version = 1.7.0_25
------ Web100 Detailed Analysis ------
Client Receive Window detected at 131760 bytes.
100 Mbps FastEthernet link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.
Web100 reports the Round trip time = 11.77 msec; the Packet size = 1448 Bytes; and
There were 169 packets retransmitted, 493 duplicate acks received, and 554 SACK blocks received
The connection stalled 17 times due to packet loss
The connection was idle 3.65 seconds (30.41%) of the time
This connection is sender limited 9.81% of the time.
This connection is network limited 90.19% of the time.
Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch
Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: ON
RFC 1323 Window Scaling: ON
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Client IP address not found. For IE users, modify the Java parameters
click Tools - Internet Options - Security - Custom Level, scroll down to
Microsoft VM - Java permissions and click Custom, click Java Custom Settings
Edit Permissions - Access to all Network Addresses, click Eanble and save changes
Any help would be appreciated! Aside from the internet, I'm really happy with Fios TV . The customer service rep credited me the internet cost for this month because of my issues and for that I am very thankful! but... I would still like to get this fixed as soon as possible.
Things I've tried:
resetting ONT
Forced firmware upgrade and router reset
Verizon reset my service and gave me a new IP

By the way, I agree with sybrand: you need to tune
your redo log size.
Regards
Ignacio
http://oracledisect.blogspot.com
Ignacio,
The excessive waits on log file parallel write and the related client wait of log file sync may be due to insufficient CPU availability, and may not point at an actual redo log size problem or a problem with the disk speed where the redo is written to disk, especially if there are 3 Oracle instances on the server with a single CPU.
Paraphrased from "Optimizing Oracle Performance":
The log file sync wait event is one of the first events to show increased latencies due to the time a process spends waiting in a CPU wait queue while processing excessive logical IOs.
Kevin Closson wrote a couple blog entries that examined the potential problems of insufficient CPU capacity and its effects on log file parallel write when writing to solid state disks, and even when writing redo was explicitly disabled:
http://kevinclosson.wordpress.com/2007/07/21/manly-men-only-use-solid-state-disk-for-redo-logging-lgwr-io-is-simple-but-not-lgwr-processing/
"Once LGWR loses his CPU it may be quite some time until he gets it back. For instance, if LGWR is preempted in the middle of trying to perform a redo buffer flush, there may be several time slices of execution for other processes before LGWR gets back on CPU..." Fix the CPU problem, and the other significant waits may decrease.
JesusLuvR,
yingkuan's suggestion to look at the SQL statement that performs the 4,365,564 logical IOs, consumes 186.03 CPU seconds, and has an execution time of 225.06 seconds, is likely a very good starting point. You might also want to check the value of the SESSION_CACHED_CURSORS parameter to see if it needs to be adjusted.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

Hostapd: packet losses

Hi,
I have hostapd running on my Arch machine and I'm experiencing some problems. To illustrate what kind of problems exactly, I'll attach this log from a connected Windows laptop (which was located right next to the access point, signal quality was 100%) (192.168.0.5 is the IP of the Arch machine):
C:\Users\popoffka>ping -n 20 ya.ru
Pinging ya.ru [77.88.21.3] with 32 bytes of data:
Request timed out.
Reply from 77.88.21.3: bytes=32 time=1078ms TTL=59
Request timed out.
Reply from 77.88.21.3: bytes=32 time=871ms TTL=59
Request timed out.
Reply from 77.88.21.3: bytes=32 time=3479ms TTL=59
Reply from 77.88.21.3: bytes=32 time=2949ms TTL=59
Reply from 77.88.21.3: bytes=32 time=42ms TTL=59
Reply from 77.88.21.3: bytes=32 time=2221ms TTL=59
Reply from 77.88.21.3: bytes=32 time=37ms TTL=59
Request timed out.
Reply from 77.88.21.3: bytes=32 time=3061ms TTL=59
Reply from 77.88.21.3: bytes=32 time=2877ms TTL=59
Reply from 77.88.21.3: bytes=32 time=2927ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 77.88.21.3: bytes=32 time=3024ms TTL=59
Request timed out.
Ping statistics for 77.88.21.3:
Packets: Sent = 20, Received = 11, Lost = 9 (45% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 3479ms, Average = 2051ms
C:\Users\popoffka>ping -n 10 192.168.0.5
Pinging 192.168.0.5 with 32 bytes of data:
Reply from 192.168.0.5: bytes=32 time=333ms TTL=64
Reply from 192.168.0.5: bytes=32 time=2204ms TTL=64
Reply from 192.168.0.5: bytes=32 time=3ms TTL=64
Reply from 192.168.0.5: bytes=32 time=1858ms TTL=64
Reply from 192.168.0.5: bytes=32 time=4ms TTL=64
Reply from 192.168.0.5: bytes=32 time=1882ms TTL=64
Reply from 192.168.0.5: bytes=32 time=11ms TTL=64
Reply from 192.168.0.5: bytes=32 time=1934ms TTL=64
Reply from 192.168.0.5: bytes=32 time=3ms TTL=64
Reply from 192.168.0.5: bytes=32 time=1884ms TTL=64
Ping statistics for 192.168.0.5:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 2204ms, Average = 1011ms
I tried pinging the same website from the access point itself and got no losses at all and no pings higher than 40ms. When I connect with a different laptop (Linux-based this time) I get pings around 200ms (both to the AP and to ya.ru) and still no losses. When I use my Android-based phone, I get no losses and no pings higher than 80ms.
I could probably blame the difference between my phone and the Linux-based laptop on the old WiFi adapter in the laptop, but my Windows laptop has a new Broadcom 43224 a/b/g/n adapter, so I'm really surprised by the incredibly high ping times and packet losses.
I don't even know where to look for a possible solution, but here's my hostapd.conf, hope it might help: http://codepad.org/jxeuFNrb (I already tried changing channels and/or changing HT40- to HT40+, but that didn't help). Does anyone know what might be the root of my problem and how to fix it?
Thanks (and sorry if my English is a little bit weird).
UPD: oh wait, it turned out that the reason for the high pings was an application I was running on the Windows machine that seemed to somehow overload the WiFi adapter. Now that I turned it off, pings are around 50 ms, but I still get lost packets sometimes (5 packets out of 50 were lost). I wonder what could be the reason for these lost packets.
Last edited by popoffka (2012-04-14 08:40:49)

If the issue only occurs with your Windows laptop, then I doubt the issue is going to be with your Arch machine (or hostapd setup).

WIFI Packet Loss/Jitter MacBook Air 11 & LION OSX 10.7.1

I started using computers more than 30 years ago when I was 5, I had my first IBM PC at the age of 10 and have never had any interest in paying over the odds for an Apple mac mainly because I saw the Mac as a kind of "Can't open nothing", one mouse buttoned retard of the computer world.
That is, until now.
I set up an online business 3 years ago and rented a dedicated server and set the whole business up in a cloud, so to speak. Having done that, all I needed a laptop for was a remote desktop connection and to run a SIP phone (Internet phone).
My PC based laptops had almost nothing installed on them, and I wasn't using software on the laptop itself, I was using remote desktop, so - why not try a MAC? The new Macbook Air 11 is small, light and made of metal and glass so should be robust enough to travel with me.
I have to say, this was the worst move I've ever made.
I opened the new shiny macbook and the first thing I noticed was that the internet seemed hit and miss. Moving around the room I managed to find a spot whereby pages woud load quickly. Strange, my £200 acer laptop was sh.t fast everywhere in the house. No matter, I packed it back away and carried on working on the Windows machine.
I've come to Newquay this week, and i've started to try and use the Macbook again in a hotel. The wireless signal in the room is low, and speedtest shows about 1 meg down and 3/4 meg up. That may sound bad to you, but remote desktop uses about 5k/sec (modem dial up speed) and the softphone, well, my Asterisk VOIP setup is confugured to use the GSM codec so that's 8k/sec each way + overheads.
This whole setup was deliberately designed to be "thin" so I can travel with ease and work on bad connections like USB internet sticks.
Anyhow, the Macbook was unable to hold a stable connection to the remote desktop or SIP phone, even though the speed test showed a whopping 1 meg up and down. What you may not be aware of is that there is more to a connection than the speed, there is the quality as well. How many packets are lost / how much "jitter" is on the line.
Anyhow, we're not living in the 3rd world, I ran a PINGTEST and it showed a small amount of jitter but told me the line was class B, online games may suffer but voip should be fine.
I unpacked the Acer, placed it in exactly the same spot as the Apple had sat in and it worked beautifully with 1 bar of wireless signal, all day long. Phone calls were clear.
So you know now what I'm thinking. I'm sitting here with my £200 acer because I can't use the £1500 macbook air 11. I paid nearly sixteen hundred pounds for this piece of .... and it doesn't ...... work. Time to contact Apple support.
2nd Mistake!
Representitive 1: - Told me that I can't compare the Macbook Air to the Acer, the Acer has Google Chrome and everybody knows Google Chrome is the fastest browser. I was told there was nothing more he could do, its probably a bad line at the hotel. When I explained the Acer works fine for voip I was told well, maybe it is getting a better signal. I explained the Acer has the cheapest possible parts inside it and paid 1500 for this macbook, expecting it to have quality parts inside and was told I'd paid for the size, because its so small but its not considered "powerful". Apple do you train your staff? Clearly not.
Thank god I wasn't paying to talk to this moron.
Representitive 2: - Had no idea what packet loss or Jitter was, got me to do a speedtest and said that looks fine. Then he got me to remove the WIFI adapter and re add it in the network settings.
Guess what, nothing changed, its still the same hardware and software.
Representitive 3: - Still not really understanding "quality" issues with the networking interface, I was asked to install the latest Java client. I did it, only because I wanted to comply with Apples wishes so they'd help me, but they weren't helping and Java has nothing to do with the network adapter, so that was useless advice too.
Apple seem to have no idea there is a problem, even though Google has pages and pages of people saying the same as me, and their own discussion forums have thousands of people complaining https://discussions.apple.com/thread/2664670?start=0&tstart=0
Finally, late yesterday whilst speaking to d.ck head number 3 at Apple support, we found a forum post talking about a fix, 10.7.1 update. I told d. head number 3 about the update and he suggested I applied it. So I did and everything looked great, for a whole evening.
This morning, I switched on again and the same thing, slow remote desktop, choppy unusable phone. Remember the phone needs less than 20k for a conversation, thats 0.2 meg. Speedtest again showing a whole meg both ways.
I called apple support again, this time being a little forceful, and I've asked for this to be escalated, but the bottom line is - they have no fix, they don't aknowledge this as a problem and I was told LION is new, so maybe it's got a bug..
I told the guy on the phone this is a network driver issue, the intermittency of the problem shows that and the Apple's lack of settings for the network adapter means the unit is autonegotiating with the router and choosing speed and duplex settings on its own. Sometimes it does that correctly, other times not and the connection although fast has a lot of noise / packet loss / corruption.
I've found a workaround, you put the unit to sleep and wake it up again and it runs fast until the next shutdown. Not really acceptable seeing as I was paying for "the cream of the crop".
I will definately not be recommending Apple products, and i'll certainly not be replacing the Windows laptops in my business with Apple's toytown system- i'd go out of business if I had to rely on this.
All there is left now, is to look at Boot camp and see if I can wipe this waste of space linux hack from the unit and install Windows 7.

I started using computers more than 30 years ago when I was 5, I had my first IBM PC at the age of 10 and have never had any interest in paying over the odds for an Apple mac mainly because I saw the Mac as a kind of "Can't open nothing", one mouse buttoned retard of the computer world.
That is, until now.
I set up an online business 3 years ago and rented a dedicated server and set the whole business up in a cloud, so to speak. Having done that, all I needed a laptop for was a remote desktop connection and to run a SIP phone (Internet phone).
My PC based laptops had almost nothing installed on them, and I wasn't using software on the laptop itself, I was using remote desktop, so - why not try a MAC? The new Macbook Air 11 is small, light and made of metal and glass so should be robust enough to travel with me.
I have to say, this was the worst move I've ever made.
I opened the new shiny macbook and the first thing I noticed was that the internet seemed hit and miss. Moving around the room I managed to find a spot whereby pages woud load quickly. Strange, my £200 acer laptop was sh.t fast everywhere in the house. No matter, I packed it back away and carried on working on the Windows machine.
I've come to Newquay this week, and i've started to try and use the Macbook again in a hotel. The wireless signal in the room is low, and speedtest shows about 1 meg down and 3/4 meg up. That may sound bad to you, but remote desktop uses about 5k/sec (modem dial up speed) and the softphone, well, my Asterisk VOIP setup is confugured to use the GSM codec so that's 8k/sec each way + overheads.
This whole setup was deliberately designed to be "thin" so I can travel with ease and work on bad connections like USB internet sticks.
Anyhow, the Macbook was unable to hold a stable connection to the remote desktop or SIP phone, even though the speed test showed a whopping 1 meg up and down. What you may not be aware of is that there is more to a connection than the speed, there is the quality as well. How many packets are lost / how much "jitter" is on the line.
Anyhow, we're not living in the 3rd world, I ran a PINGTEST and it showed a small amount of jitter but told me the line was class B, online games may suffer but voip should be fine.
I unpacked the Acer, placed it in exactly the same spot as the Apple had sat in and it worked beautifully with 1 bar of wireless signal, all day long. Phone calls were clear.
So you know now what I'm thinking. I'm sitting here with my £200 acer because I can't use the £1500 macbook air 11. I paid nearly sixteen hundred pounds for this piece of .... and it doesn't ...... work. Time to contact Apple support.
2nd Mistake!
Representitive 1: - Told me that I can't compare the Macbook Air to the Acer, the Acer has Google Chrome and everybody knows Google Chrome is the fastest browser. I was told there was nothing more he could do, its probably a bad line at the hotel. When I explained the Acer works fine for voip I was told well, maybe it is getting a better signal. I explained the Acer has the cheapest possible parts inside it and paid 1500 for this macbook, expecting it to have quality parts inside and was told I'd paid for the size, because its so small but its not considered "powerful". Apple do you train your staff? Clearly not.
Thank god I wasn't paying to talk to this moron.
Representitive 2: - Had no idea what packet loss or Jitter was, got me to do a speedtest and said that looks fine. Then he got me to remove the WIFI adapter and re add it in the network settings.
Guess what, nothing changed, its still the same hardware and software.
Representitive 3: - Still not really understanding "quality" issues with the networking interface, I was asked to install the latest Java client. I did it, only because I wanted to comply with Apples wishes so they'd help me, but they weren't helping and Java has nothing to do with the network adapter, so that was useless advice too.
Apple seem to have no idea there is a problem, even though Google has pages and pages of people saying the same as me, and their own discussion forums have thousands of people complaining https://discussions.apple.com/thread/2664670?start=0&tstart=0
Finally, late yesterday whilst speaking to d.ck head number 3 at Apple support, we found a forum post talking about a fix, 10.7.1 update. I told d. head number 3 about the update and he suggested I applied it. So I did and everything looked great, for a whole evening.
This morning, I switched on again and the same thing, slow remote desktop, choppy unusable phone. Remember the phone needs less than 20k for a conversation, thats 0.2 meg. Speedtest again showing a whole meg both ways.
I called apple support again, this time being a little forceful, and I've asked for this to be escalated, but the bottom line is - they have no fix, they don't aknowledge this as a problem and I was told LION is new, so maybe it's got a bug..
I told the guy on the phone this is a network driver issue, the intermittency of the problem shows that and the Apple's lack of settings for the network adapter means the unit is autonegotiating with the router and choosing speed and duplex settings on its own. Sometimes it does that correctly, other times not and the connection although fast has a lot of noise / packet loss / corruption.
I've found a workaround, you put the unit to sleep and wake it up again and it runs fast until the next shutdown. Not really acceptable seeing as I was paying for "the cream of the crop".
I will definately not be recommending Apple products, and i'll certainly not be replacing the Windows laptops in my business with Apple's toytown system- i'd go out of business if I had to rely on this.
All there is left now, is to look at Boot camp and see if I can wipe this waste of space linux hack from the unit and install Windows 7.

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.

DATA PACKET LOSS! Websites SLOW!

Similar Messages

Maybe you are looking for