dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
3
share rss forum feed


Irish Shark
Play Like A Champion Today
Premium,MVM
join:2000-07-29
Las Vegas, NV
kudos:4
reply to GamerQwest87

Re: Netalyzer Shows: Uplink 540ms "Excessive Buffering"

• In your test this tracert is there.

Traceroute (?): OK 
 
It takes 14 network hops for traffic to pass from our server to your system, as shown below. For each hop, the time it takes to traverse it is shown in parentheses.
 
    10.209.112.3 (0 ms)
    ip-10-1-14-13.ec2.internal (0 ms)
    ip-10-1-172-130.ec2.internal (0 ms)
    ip-10-1-172-187.ec2.internal (0 ms)
    *
    *
    *
    100.64.16.21 (0 ms)
    205.251.245.66 (0 ms)
    72.21.222.146 (1 ms)
    dca2-edge-02.inet.qwest.net (2 ms)
    dca2-edge-01.inet.qwest.net (2 ms)
    phnx-dsl-gw62-234.phnx.qwest.net (73 ms)
    174-19-152-56.phnx.qwest.net (100 ms)
 

• The analysis also says:

"Path MTU (?): OK
The path between your network and our system supports an MTU of at least 1500 bytes, and the path between our system and your network has an MTU of 1492 bytes. The bottleneck is at IP address 75.160.237.234."

Which is not true, since you are on PPPoE and the MTU is correctly set at 1492.

However it does point to the hop just before yours with a 73 ms RTT and then your hop with a 100 ms RTT.

********
• Here is what I get to that router:
Traceroute has started
 
traceroute to 75.160.237.234 (75.160.237.234), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  1.063 ms  0.799 ms  0.856 ms
 2  10.66.128.1 (10.66.128.1)  8.307 ms  9.277 ms  7.933 ms
 3  24-234-16-125.ptp.lvcm.net (24.234.16.125)  7.435 ms  47.007 ms  9.380 ms
 4  24-234-6-29.ptp.lvcm.net (24.234.6.29)  8.720 ms  8.411 ms  9.550 ms
 5  24-234-6-218.ptp.lvcm.net (24.234.6.218)  8.526 ms  41.176 ms  8.370 ms
 6  68.1.5.137 (68.1.5.137)  20.851 ms *  21.221 ms
 7  xe-7-0-2.edge2.losangeles9.level3.net (4.53.230.37)  25.287 ms  22.268 ms  22.684 ms
 8  ae-3-80.edge1.losangeles9.level3.net (4.69.144.138)  14.147 ms  14.868 ms  13.772 ms
 9  lap-brdr-03.inet.qwest.net (63.146.27.33)  21.392 ms  21.491 ms  30.629 ms
10  * * *
11  phnx-dsl-gw62-234.phnx.qwest.net (75.160.237.234)  26.835 ms  27.973 ms  27.327 ms
 

Ping has started
 
PING 75.160.237.234 (75.160.237.234): 56 data bytes
64 bytes from 75.160.237.234: icmp_seq=0 ttl=244 time=28.997 ms
64 bytes from 75.160.237.234: icmp_seq=1 ttl=244 time=28.053 ms
64 bytes from 75.160.237.234: icmp_seq=2 ttl=244 time=27.840 ms
64 bytes from 75.160.237.234: icmp_seq=3 ttl=244 time=26.971 ms
64 bytes from 75.160.237.234: icmp_seq=4 ttl=244 time=28.422 ms
64 bytes from 75.160.237.234: icmp_seq=5 ttl=244 time=27.140 ms
64 bytes from 75.160.237.234: icmp_seq=6 ttl=244 time=26.406 ms
64 bytes from 75.160.237.234: icmp_seq=7 ttl=244 time=29.572 ms
64 bytes from 75.160.237.234: icmp_seq=8 ttl=244 time=27.649 ms
64 bytes from 75.160.237.234: icmp_seq=9 ttl=244 time=26.711 ms
 
--- 75.160.237.234 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 26.406/27.776/29.572/0.964 ms
 

• And Finally a tracert to your hop.
Traceroute has started
 
traceroute to 174.19.152.56 (174.19.152.56), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  0.970 ms  0.778 ms  0.806 ms
 2  10.66.128.1 (10.66.128.1)  7.666 ms  7.951 ms  7.599 ms
 3  24-234-16-125.ptp.lvcm.net (24.234.16.125)  8.128 ms  8.140 ms  7.948 ms
 4  24-234-6-29.ptp.lvcm.net (24.234.6.29)  8.617 ms  15.715 ms  8.207 ms
 5  24-234-6-218.ptp.lvcm.net (24.234.6.218)  7.043 ms  8.023 ms  7.626 ms
 6  68.1.5.137 (68.1.5.137)  21.173 ms  22.025 ms  21.816 ms
 7  xe-5-0-1.edge2.losangeles9.level3.net (4.53.230.85)  21.892 ms  22.044 ms  21.771 ms
 8  ae-1-60.edge1.losangeles9.level3.net (4.69.144.10)  68.330 ms  13.925 ms  14.964 ms
 9  lap-brdr-03.inet.qwest.net (63.146.27.33)  57.489 ms  20.811 ms  22.128 ms
10  * * *
11  phnx-dsl-gw62-234.phnx.qwest.net (75.160.237.234)  26.064 ms  25.863 ms  25.700 ms
12  * * *
13  * * *
14  * * *
 

Since your firewall is up I cannot get a RTT to your hop, but the last hop is the same router that I cannot find anything wrong with it at this point in time.

• Based on this data either you have an issue at your hop, or that test is pure BS.

I say that because it gave me pretty much the same wording that is in your test.

• So, I don't know what you want to do at this juncture. Do you what to dig some more, or try your gaming and see is you still have issues?

• Another possibility is that the "buffering" is just the winds on the Internet and it could be off of CLs network which they have no control.

--
"You can observe a lot by watching". Yogi Berra

GamerQwest87

join:2012-08-07
Phoenix, AZ

1 edit

I didn't think my firewall was actually up. I know the PC firewall is off and I thought my modem/router firewall was turned off also. However, I just checked it and it seemed to be on. I'll turn it off, re-test and also test in-game to see if there is any difference in change and report back if there is still problems.

/Edit:

Turned off the firewall, both the IPv4 and IPv6 firewalls to be sure and the issue didn't change in any way.



Irish Shark
Play Like A Champion Today
Premium,MVM
join:2000-07-29
Las Vegas, NV
kudos:4

• I cannot get to 174.19.152.56 (which if I reading things correctly this is your IP).

• Tracert to that router

traceroute to 75.160.237.234 (75.160.237.234), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  1.216 ms  0.831 ms  0.799 ms
 2  10.66.128.1 (10.66.128.1)  8.814 ms  7.855 ms  8.111 ms
 3  24-234-16-125.ptp.lvcm.net (24.234.16.125)  8.226 ms  7.585 ms  8.021 ms
 4  24-234-6-29.ptp.lvcm.net (24.234.6.29)  8.621 ms  7.522 ms  8.553 ms
 5  24-234-6-218.ptp.lvcm.net (24.234.6.218)  10.439 ms  8.538 ms  18.041 ms
 6  68.1.5.137 (68.1.5.137)  20.632 ms  21.834 ms  22.887 ms
 7  xe-7-0-2.edge2.losangeles9.level3.net (4.53.230.37)  30.921 ms  21.226 ms  21.641 ms
 8  * * *
 9  lap-brdr-03.inet.qwest.net (63.146.27.33)  22.499 ms  23.690 ms  22.309 ms
10  * * *
11  phnx-dsl-gw62-234.phnx.qwest.net (75.160.237.234)  26.025 ms  25.770 ms  27.716 ms
 

• Ping to that router
PING 75.160.237.234 (75.160.237.234): 56 data bytes
64 bytes from 75.160.237.234: icmp_seq=0 ttl=244 time=27.943 ms
64 bytes from 75.160.237.234: icmp_seq=1 ttl=244 time=26.198 ms
64 bytes from 75.160.237.234: icmp_seq=2 ttl=244 time=25.917 ms
64 bytes from 75.160.237.234: icmp_seq=3 ttl=244 time=25.393 ms
64 bytes from 75.160.237.234: icmp_seq=4 ttl=244 time=28.786 ms
64 bytes from 75.160.237.234: icmp_seq=5 ttl=244 time=27.492 ms
64 bytes from 75.160.237.234: icmp_seq=6 ttl=244 time=25.404 ms
64 bytes from 75.160.237.234: icmp_seq=7 ttl=244 time=26.246 ms
64 bytes from 75.160.237.234: icmp_seq=8 ttl=244 time=26.331 ms
64 bytes from 75.160.237.234: icmp_seq=9 ttl=244 time=25.245 ms
 
--- 75.160.237.234 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 25.245/26.495/28.786/1.132 ms
 

--
"You can observe a lot by watching". Yogi Berra