Pings

[equk]

atm ping seems a lot lower, still unstable but here is a traceroute (23:00)

Code Select Expand

traceroute to 194.109.69.93 (194.109.69.93), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  1.293 ms  0.698 ms  0.660 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  23.731 ms  21.754 ms  23.975 ms
3  * telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  22.002 ms  20.796 ms
4  telehouse-gw.idnet.net (212.69.40.1)  22.035 ms  22.655 ms  25.568 ms
5  redbus-gw.idnet.net (212.69.63.1)  26.335 ms  22.084 ms *
6  ams-ix.sara.xs4all.net (195.69.144.48)  40.124 ms  40.001 ms  39.974 ms
7  0.so-6-0-0.xr2.3d12.xs4all.net (194.109.5.5)  48.126 ms  39.984 ms  39.911 ms
8  0.so-3-0-0.cr2.3d12.xs4all.net (194.109.5.94)  40.053 ms  39.894 ms  37.924 ms
9  quake3-04.xs4all.nl (194.109.69.93)  39.994 ms *  50.579 ms
still higher than expected but a lot different from 130+ms

strange how it's ok certain times of the day

[maxping]

strange how it's ok certain times of the day

Using Virtual ping i get the results below - Minimum = 48ms, Maximum = 60ms, Average = 51ms

Only 1 big hop to 60ms then most 50 - 55 yet the l8nc graph shows big blue spikes,to be honest i am not bothering with it anymore i don't think its reliable.
I will stick to the xp command prompt to trace or use Virtual ping.
I don't seem to be seeing the big lag spikes others are seeing.(bear in mind i cannot get a ping below 50ms because of interleaving) so i would say at the moment my connection is fairly stable.

Pinging 217.146.93.36 with 32 bytes of data:
Reply from 217.146.93.36 bytes:32 Time:50ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:50ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:48ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:56ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:50ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:51ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:51ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:52ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:53ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:50ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:53ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:50ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:49ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:48ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:49ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:50ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:51ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:60ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:49ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:50ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:49ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:56ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:48ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:51ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:52ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:49ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:50ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:51ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:49ms TTL:123
Reply from 217.146.93.36 bytes:32 Time:53ms TTL:123
Ping statistics for 217.146.93.36 :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 60ms, Average = 51ms

[equk]

here's some images of ingame ping graphs:

Plusnet stable @ 40ms
IDNet 130ms unstable
IDNet raise from 50 to 130 unstable



all to the same server on same setup, same router etc. Massive Difference

hmm are img tags not working?

[maxping]

all to the same server on same setup, same router etc. Massive Difference

Whats the ip i will give it a try?

[equk]

all to the same server on same setup, same router etc. Massive Difference

Whats the ip i will give it a try?

194.109.69.93:27960

quake3 3wave ctfs

[browney]

Tracing route to quake3-04.xs4all.nl [194.109.69.93]
over a maximum of 30 hops:

  1     4 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    29 ms    28 ms    29 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    31 ms    29 ms    29 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    31 ms    32 ms    31 ms  redbus-gw.idnet.net [212.69.63.1]
  5    46 ms    46 ms    46 ms  ams-ix.sara.xs4all.net [195.69.144.48]
  6    47 ms   106 ms    47 ms  0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
  7    48 ms    46 ms    47 ms  0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
  8    48 ms    46 ms    47 ms  quake3-04.xs4all.nl [194.109.69.93]

Trace complete.


Pinging 194.109.69.93 with 32 bytes of data:

Reply from 194.109.69.93: bytes=32 time=48ms TTL=248
Reply from 194.109.69.93: bytes=32 time=47ms TTL=248
Reply from 194.109.69.93: bytes=32 time=46ms TTL=248
Reply from 194.109.69.93: bytes=32 time=46ms TTL=248

Ping statistics for 194.109.69.93:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 46ms, Maximum = 48ms, Average = 46ms

[maxping]

Its put  15ms onto my average so not as bad as i had expected.


Pinging 194.109.69.93 with 32 bytes of data:
Reply from 194.109.69.93 bytes:32 Time:66ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:66ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:67ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:65ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:65ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:65ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:66ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:65ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:66ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:65ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:66ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:66ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:67ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:66ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:68ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:65ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:67ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:69ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:71ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:66ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:66ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:64ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:70ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:65ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:65ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:72ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:67ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:64ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:65ms TTL:248
Reply from 194.109.69.93 bytes:32 Time:65ms TTL:248
Ping statistics for 194.109.69.93 :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 72ms, Average = 66ms

[browney]

Tracing route to core1.multiplay.co.uk [85.236.96.22]
over a maximum of 30 hops:

  1     4 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    28 ms    28 ms    28 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    31 ms    28 ms    30 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    48 ms   212 ms   214 ms  lonap2.enta.net [193.203.5.135]
  5    30 ms    29 ms    30 ms  redbus-sov3.core.enta.net [84.45.193.206]
  6    30 ms    32 ms    33 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  7    29 ms    30 ms    29 ms  www1.multiplay.co.uk [85.236.96.22]

Trace complete.

C:\Documents and Settings\Steven Brown>tracert www.multiplay.co.uk

Tracing route to core1.multiplay.co.uk [85.236.96.22]
over a maximum of 30 hops:

  1     4 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    29 ms    29 ms    28 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    30 ms    30 ms    30 ms  telehouse-gw.idnet.net [212.69.40.1]
  4   153 ms   214 ms   209 ms  lonap2.enta.net [193.203.5.135]
  5    31 ms    29 ms    30 ms  redbus-sov3.core.enta.net [84.45.193.206]
  6    30 ms    29 ms    31 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  7    31 ms    30 ms    30 ms  www1.multiplay.co.uk [85.236.96.22]

Trace complete.


Any one else see who IDNet should cut out? 

[equk]

Code Select Expand

traceroute to core1.multiplay.co.uk (85.236.96.22), 30 hops max, 40 byte packets 1  cisco (192.168.1.1)  1.374 ms  0.697 ms  0.669 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  22.802 ms  23.782 ms *
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  23.154 ms  23.291 ms  22.061 ms
4  telehouse-gw.idnet.net (212.69.40.1)  23.981 ms  22.015 ms  23.816 ms
5  * lonap2.enta.net (193.203.5.135)  22.598 ms  22.725 ms
6  redbus-sov3.core.enta.net (84.45.193.206)  22.057 ms  22.388 ms  22.024 ms
7  gi4-3.enta-transit.as35028.net (84.45.252.122)  171.934 ms  24.434 ms  23.883 ms
8  www1.multiplay.co.uk (85.236.96.22)  23.978 ms  22.584 ms *

hmm bit of a spike there 171ms!? from 20 that's a big leap

[equk]

hmm fastest speed test so far (it is 01:34 tho)

http://www.speedtest.bbmax.co.uk/results.php?t=1157502684&v=402944

Date of Speed Test:     2006-09-06 01:31:24
Download Speed:    1865 kbps (233.1 KB/sec transfer rate)
Upload Speed:    237 kbps (29.6 KB/sec transfer rate)

seems a bit better I guess still shame about these ping problems

[xms]

XMS could you run l8nc here  http://www.l8nc.com/l8nc.php and paste the results for a couple of hours?

Just registered - but i'm guessing i need to set my router not to drop pings?

Yup.  It'll certainly be very helpful when you do this, as personally I have some doubts about this reverse ping as a method of diagnosing forward ping problems based on my own empirical tests, but it would be good to see more hard evidence one way or the other.

Here ya go...



and....

Tracing route to www1.multiplay.co.uk [85.236.96.22]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.254.254
  2     9 ms     9 ms     9 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    11 ms    10 ms    10 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    10 ms    11 ms    11 ms  lonap2.enta.net [193.203.5.135]
  5    10 ms    10 ms    11 ms  redbus-sov3.core.enta.net [84.45.193.206]
  6    10 ms    10 ms    11 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  7    11 ms    10 ms    10 ms  www1.multiplay.co.uk [85.236.96.22]

Trace complete.

[AvengerUK]

XMS could you run l8nc here  http://www.l8nc.com/l8nc.php and paste the results for a couple of hours?

Just registered - but i'm guessing i need to set my router not to drop pings?

Yup.  It'll certainly be very helpful when you do this, as personally I have some doubts about this reverse ping as a method of diagnosing forward ping problems based on my own empirical tests, but it would be good to see more hard evidence one way or the other.

Here ya go...



and....

Tracing route to www1.multiplay.co.uk [85.236.96.22]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.254.254
  2     9 ms     9 ms     9 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    11 ms    10 ms    10 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    10 ms    11 ms    11 ms  lonap2.enta.net [193.203.5.135]
  5    10 ms    10 ms    11 ms  redbus-sov3.core.enta.net [84.45.193.206]
  6    10 ms    10 ms    11 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  7    11 ms    10 ms    10 ms  www1.multiplay.co.uk [85.236.96.22]

Trace complete.

so you to have the ping spikes - my graph is almost the same as that aswell, it simply cant be our routers that cause the issue. I have to say that im unsure why simon thinks this could be the case, along with bringing the poor (very poor) line stats etc into the equation - when evedently many users have the problem!, it has me slightly worried!

[xms]

What i don't get tho is how this is affecting some peoples gaming and not others.

To me, ICMP ping doesnt really mean anything. I get consistently low pings in Counter Strike, and as i said earlier - i'm REALLY critical of lag when playing in game.

I even go as far as to keep the in-game net graph open to monitor for loss etc - and have never noticed anything out of the ordinary.

I do agree that its highly unlikely to be a router issue - as mine has been problem free for over 2 years.

[AvengerUK]

It really depends on what games you play. CSS wouldent mind the ping spikes as much as other games (Usually whose net code is not aswell written) - For example, Joint operations is hard to play when a spike occurs - and you cirtianally cant hit anything! - the same is true for games such as "Halo" and "Freelancer".

- However with me, its not just the ping spikes that cause a headache, theres also the constant high pings that occur randomly and stay for a few hours

[equk]

hmm seems to be back up to 145ms to the gateway again now, last night seemed to be a lot better altho still unstable. Seems like times of the day when the net is not busy ping times are ok (altho still unstable)

I signed up for l8nc yesterday but my account still says awaiting administrator approval or something   

Code Select Expand

traceroute to core1.multiplay.co.uk (85.236.96.22), 30 hops max, 40 byte packets 1  cisco (192.168.1.1)  1.281 ms  0.657 ms  0.676 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  145.254 ms  137.174 ms  155.872 ms
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  169.948 ms  174.515 ms  167.778 ms
4  telehouse-gw.idnet.net (212.69.40.1)  166.057 ms  132.993 ms  123.822 ms
5  lonap2.enta.net (193.203.5.135)  141.963 ms  113.010 ms  115.913 ms
6  redbus-sov3.core.enta.net (84.45.193.206)  113.930 ms  118.733 ms  107.848 ms
7  gi4-3.enta-transit.as35028.net (84.45.252.122)  100.078 ms  116.770 ms  119.895 ms
8  www1.multiplay.co.uk (85.236.96.22)  107.969 ms  107.184 ms  105.789 ms


[equk]

tbh this is a waste of time, a 56k modem connection would be more stable.

also altho idnet seem willing and phone you back etc, has anyone seen anything done about this problem?

so far the response we've had is "it's your router, try another" well we've tried a total of 9 routers (7 different chipsets) and 2 modems (both with different chipsets also). So is it us who are wrong?

also on connecting to the bttest/btspeedtest connection ping times to the gateway are 16ms in the day, the pings to the idnet gateway are 100+ms (at the same time of the day). Still a router issue?

It has to be something common to us all, the only thing there (to our knowledge) seems to be idnet. Even the people who say they don't have problems, on using ping graphs are shown a number of spikes also a lot of the traceroutes have spikes from 20ms to 100+ms (even people who "don't have a problem").

Maybe there are 2 seperate problems but it still needs to be sorted. No-one will be able to play online FPS games at 130-200ms ping times. I don't think it's that bad to expect better. The cost isn't the cheapest and the expectations are high due to the reviews etc on adslguide but appart from the odd phonecall there's nothing to back this up as the actual product we're paying for isn't being provided at the standard expected.

It is almost as if it's a throughput problem as people have said, as at times of the day when you'd expect it not to be busy the ping times are suddenly better  co-incidence?

I really can't believe it's still not been sorted and am annoyed that the customers hardware is getting blamed for the problems. Has something changed suddenly to cause router/modem incompatability?

[AvengerUK]

Insert Quote 
tbh this is a waste of time, a 56k modem connection would be more stable.

/agree - 200ms constant ping is better than a 20-30ms unstable one! Consistancy is the key!

also altho idnet seem willing and phone you back etc, has anyone seen anything done about this problem?

so far the response we've had is "it's your router, try another" well we've tried a total of 9 routers (7 different chipsets) and 2 modems (both with different chipsets also). So is it us who are wrong?

the problem has apparently been and is being looked into - thats all as far as im aware

actual product we're paying for isn't being provided at the standard expected.

Unfourtunatly they are providing the product specified - there is no standards for pings!

I really can't believe it's still not been sorted and am annoyed that the customers hardware is getting blamed for the problems. Has something changed suddenly to cause router/modem incompatability?

Not as im aware, but it is indeed worrying that customers hardware is being looked into....

[thetrevone]

equk

also altho idnet seem willing and phone you back etc, has anyone seen anything done about this problem?

Although I don't find this a problem as I don't play games I do see the problem. I sense there is a growing feeling that whilst everybody believes that IDnet is doing all they can to resolve the issue there is a lack of on going communication regarding this here from them. Whilst nothing may have changed regarding a solution, a regular update would allay fears that the issue may have been forgotten or moved down the order of priorities.  I for one would hate this forum to be populated with the meaningless and inaccurate status reports that are synonymous with IP's such as Plusnet, but perhaps an update once a week would help?
Regards
Doug

[golden]

i have just done a reverse tracert from giganews

news.giganews.com

1 gw-vlan201.dca.giganews.com (216.196.98.1) 0 ms 0 ms 0 ms
2 g3-16.gw2.dca.giganews.com (216.196.96.61) 0 ms 0 ms 0 ms
3 217-6-48-249.vhost.placenetwork.de (217.6.48.249) 0 ms 0 ms 0 ms
4 linx-gw12.LON.GB.net.DTAG.DE (62.154.15.154) 73 ms 73 ms 73 ms
5 62.156.139.142 (62.156.139.142) 74 ms 74 ms 74 ms
6 sl-gw21-lon-1-1.sprintlink.net (213.206.128.102) 74 ms 74 ms 74 ms
7 idnet-b-1.arbinet.net (213.232.65.101) 73 ms 73 ms 73 ms
8 telehouse-bb-gw5.idnet.net (212.69.40.11) 73 ms 74 ms 73 ms
9 * * *
10 * * *
11 * * *
Max number of unresponsive hops reached (firewall or filter?)
news-europe.giganews.com

1 216-196-110-3.ams.giganews.com (216.196.110.3) 1 ms 0 ms 0 ms
2 ams-ix-gw.idnet.net.uk (195.69.144.141) 16 ms 15 ms 15 ms
3 telehouse-gw.idnet.net (212.69.63.2) 16 ms 18 ms 16 ms
4 telehouse-bb-gw5.idnet.net (212.69.40.11) 15 ms 16 ms 16 ms
5 * * *
6 * * *
7 * * *
Max number of unresponsive hops reached (firewall or filter?)

but going the other way it is on 300 hundred mark

richard

[equk]

here's my traceroute of giganews:

Code Select Expand

traceroute to news.giganews.com (216.196.109.144), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  1.274 ms  0.658 ms  0.637 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  138.213 ms  126.184 ms  127.920 ms
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  123.864 ms  130.659 ms  139.763 ms
4  telehouse-gw.idnet.net (212.69.40.1)  145.726 ms  152.255 ms  153.898 ms
5  ge2-2.fr1.lon.llnw.net (193.203.5.68)  168.005 ms  166.741 ms  149.915 ms
6  ag1-16-1.ar1.lon.llnw.net (68.142.84.238)  153.947 ms  150.903 ms  155.802 ms
7  agg1-15-2-4xoc48.ar1.ams.llnw.net (69.28.172.90)  169.974 ms  160.968 ms  151.684 ms
8  tge6-2.fr1.ams.llnw.net (69.28.172.85)  156.145 ms  165.321 ms  155.228 ms
9  giganews.ve212.fr1.ams.llnw.net (87.248.196.14)  165.960 ms  184.749 ms  165.854 ms
10  * * *

[AvengerUK]

here's my traceroute of giganews:

Code Select Expand

traceroute to news.giganews.com (216.196.109.144), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  1.274 ms  0.658 ms  0.637 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  138.213 ms  126.184 ms  127.920 ms
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  123.864 ms  130.659 ms  139.763 ms
4  telehouse-gw.idnet.net (212.69.40.1)  145.726 ms  152.255 ms  153.898 ms
5  ge2-2.fr1.lon.llnw.net (193.203.5.68)  168.005 ms  166.741 ms  149.915 ms
6  ag1-16-1.ar1.lon.llnw.net (68.142.84.238)  153.947 ms  150.903 ms  155.802 ms
7  agg1-15-2-4xoc48.ar1.ams.llnw.net (69.28.172.90)  169.974 ms  160.968 ms  151.684 ms
8  tge6-2.fr1.ams.llnw.net (69.28.172.85)  156.145 ms  165.321 ms  155.228 ms
9  giganews.ve212.fr1.ams.llnw.net (87.248.196.14)  165.960 ms  184.749 ms  165.854 ms
10  * * *

Ouch!

[mrapoc]

imo this could be down to max, anyone on 2mbps getting this problem?

[AvengerUK]

imo this could be down to max, anyone on 2mbps getting this problem?

Yes...EQUK!!!

http://www.l8nc.com/graph.php?jid=58e61f6e3d3d258ec640ec3f21295d2e - Oh god...here we go again ffs!

[equk]

imo this could be down to max, anyone on 2mbps getting this problem?

I was hoping it was a MAX problem but I guess it's not as I'm on 2mb fixed now and it's just the same.

Code Select Expand

Downstream Upstream
SNR Margin 12.4 28.0 dB
Line Attenuation52.4 30.5 dB
Data Rate 2272 288 kbps
Latency FAST FAST
However on the fixed service I at least don't get the disconnects I was getting on max. Shame about the ping times 

[maxping]

imo this could be down to max, anyone on 2mbps getting this problem?

Hey leave me out of it