I'm in St. Lucia on BPA and recently my connection has become s***. Last time I played a game was a few months ago and it was all good up to then. Recently I've tried to play again and been getting constant 4% packetloss spiking up to 10, and pings have been spiking all over the shop too. Makes it s*** to play. Surfing the web it seems to get stuck quite often too.


Pinging gamearena.com.au [144.140.172.7] with 32 bytes of data:

Reply from 144.140.172.7: bytes=32 time=44ms TTL=247
Reply from 144.140.172.7: bytes=32 time=21ms TTL=247
Reply from 144.140.172.7: bytes=32 time=21ms TTL=247
Reply from 144.140.172.7: bytes=32 time=21ms TTL=247
Reply from 144.140.172.7: bytes=32 time=21ms TTL=247
Reply from 144.140.172.7: bytes=32 time=21ms TTL=247
Reply from 144.140.172.7: bytes=32 time=21ms TTL=247
Reply from 144.140.172.7: bytes=32 time=21ms TTL=247
Reply from 144.140.172.7: bytes=32 time=21ms TTL=247
Reply from 144.140.172.7: bytes=32 time=21ms TTL=247
Reply from 144.140.172.7: bytes=32 time=22ms TTL=247
Reply from 144.140.172.7: bytes=32 time=22ms TTL=247
Reply from 144.140.172.7: bytes=32 time=21ms TTL=247
Reply from 144.140.172.7: bytes=32 time=22ms TTL=247
Reply from 144.140.172.7: bytes=32 time=208ms TTL=247
Reply from 144.140.172.7: bytes=32 time=22ms TTL=247
Reply from 144.140.172.7: bytes=32 time=21ms TTL=247
Reply from 144.140.172.7: bytes=32 time=23ms TTL=247
Reply from 144.140.172.7: bytes=32 time=23ms TTL=247
Reply from 144.140.172.7: bytes=32 time=208ms TTL=247

Ping statistics for 144.140.172.7:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 208ms, Average = 41ms



Any one else having problems? Don't suppose there's anything I can do...?

Post some traceroutes?

all the uni & college kids are back & downloading the latest greys anatomy, chewing up your internet. mmhmmm

yeah getting similar problems here, located at lutwyche.

I tried to tracert www.gamearena.com.au but after the first line it just timed out completely? Not sure why...

Will try again later

cos bpa don't respond to icmp on that hop and windows traceroute is icmp, not udp

did you let it go a bit longer? it should start responding to the hops after that

last edited by Jim at 09:58:42 14/Feb/07

ah yeah that's totally wrong, just hopped into my home machine and tried it and I see what you mean

get a decent isp

give this a burl:
http://www.r1ch.net/stuff/ftrace/

you'll get no answer from the endpoint using udp cos it'll be filtered by our firewall, but you'll at least get all the points between


ftrace -u www.gamearena.com.au

Tracing route to 144.140.172.7 with TTL of 32:

1 2ms 1ms 1ms 192.168.1.1
2 15ms 8ms 8ms 10.49.96.1
3 12ms 10ms 9ms 58.160.20.1
4 9ms 10ms 8ms 58.160.23.246
5 13ms 9ms 11ms CPE-61-9-210-8.qld.bigpond.net.au [61.9.210.8]
6 13ms 9ms 9ms TenGigabitEthernet7-3.woo4.Brisbane.telstra.net [165.228.107.193]
7 12ms 13ms 9ms TenGigE0-8-0-2.woo-core1.Brisbane.telstra.net [203.50.51.129]
8 23ms 20ms 24ms Pos0-4-1-0.chw-core2.Sydney.telstra.net [203.50.6.201]
9 22ms 39ms 22ms TenGigabitEthernet8-1.pit2.Sydney.telstra.net [203.50.20.184]
10 23ms 25ms 30ms pitt13-colo-r02 [139.130.185.250]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 ^C

Mine completes fine.

Tracing route to 144.140.172.7 with TTL of 32:

1 3ms 0ms 0ms 192.168.0.1
2 10ms 9ms 10ms 172.18.112.209
3 9ms 8ms 9ms 172.18.70.58
4 9ms 9ms 9ms CPE-61-9-210-7.qld.bigpond.net.au [61.9.210.7]
5 8ms 9ms 9ms TenGigabitEthernet9-3.woo2.Brisbane.telstra.net [139.130.185.181]
6 10ms 9ms 10ms TenGigE0-8-0-2.woo-core1.Brisbane.telstra.net [203.50.51.129]
7 20ms 20ms 20ms Pos0-4-1-0.chw-core2.Sydney.telstra.net [203.50.6.201]
8 20ms 21ms 20ms TenGigabitEthernet8-1.pit2.Sydney.telstra.net [203.50.20.184]
9 21ms 20ms 20ms pitt13-colo-r02 [139.130.185.250]
10 20ms 21ms 21ms 144.140.172.5
11 20ms 21ms 20ms 144.140.172.7

Traceroute complete.

bigpond dsl LOOOOOOOOOOOOOOOL

i would go with grey's anatomy theory