Forum Home
Press F1
Thread ID: 53432	2005-01-17 08:35:00	IHUG crappy ping	ech3lon (5824)	Press F1

Post ID	Timestamp	Content	User
315066	2005-01-17 08:35:00	I'm on IHUG bliink account (adsl 256k) and normally the ping to local address is around 40 to 80 ms but about a month ago the ping started to climb up. Now it has reach around 200+ ms, anyone know how this happen? I mean, this 'dial-up' ping is not exactly the the best for playing fps on the net. This is the capture from ping command "ping ihug.co.nz" Pinging ihug.co.nz [203.109.252.75] with 32 bytes of data: Reply from 203.109.252.75: bytes=32 time=210ms TTL=60 Reply from 203.109.252.75: bytes=32 time=213ms TTL=60 Reply from 203.109.252.75: bytes=32 time=241ms TTL=60 Reply from 203.109.252.75: bytes=32 time=232ms TTL=60 Ping statistics for 203.109.252.75: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 210ms, Maximum = 241ms, Average = 224ms	ech3lon (5824)
315067	2005-01-17 08:54:00	Here are my results: PING ihug.co.nz (203.109.252.75): 56 data bytes 64 bytes from 203.109.252.75: icmp_seq=0 ttl=53 time=159.724 ms 64 bytes from 203.109.252.75: icmp_seq=1 ttl=53 time=160.043 ms 64 bytes from 203.109.252.75: icmp_seq=2 ttl=53 time=150.168 ms 64 bytes from 203.109.252.75: icmp_seq=3 ttl=53 time=150.169 ms 64 bytes from 203.109.252.75: icmp_seq=4 ttl=53 time=150.188 ms 64 bytes from 203.109.252.75: icmp_seq=5 ttl=53 time=160.172 ms 64 bytes from 203.109.252.75: icmp_seq=6 ttl=53 time=150.260 ms 64 bytes from 203.109.252.75: icmp_seq=7 ttl=53 time=150.200 ms 64 bytes from 203.109.252.75: icmp_seq=8 ttl=53 time=160.229 ms 64 bytes from 203.109.252.75: icmp_seq=9 ttl=53 time=160.158 ms 64 bytes from 203.109.252.75: icmp_seq=10 ttl=53 time=560.193 ms 64 bytes from 203.109.252.75: icmp_seq=11 ttl=53 time=751.072 ms 64 bytes from 203.109.252.75: icmp_seq=12 ttl=53 time=989.994 ms 64 bytes from 203.109.252.75: icmp_seq=13 ttl=53 time=170.178 ms 64 bytes from 203.109.252.75: icmp_seq=14 ttl=53 time=160.190 ms 64 bytes from 203.109.252.75: icmp_seq=15 ttl=53 time=160.181 ms 64 bytes from 203.109.252.75: icmp_seq=16 ttl=53 time=160.178 ms 64 bytes from 203.109.252.75: icmp_seq=17 ttl=53 time=160.057 ms 64 bytes from 203.109.252.75: icmp_seq=18 ttl=53 time=160.169 ms 64 bytes from 203.109.252.75: icmp_seq=19 ttl=53 time=150.218 ms 64 bytes from 203.109.252.75: icmp_seq=20 ttl=53 time=160.157 ms 64 bytes from 203.109.252.75: icmp_seq=21 ttl=53 time=160.171 ms 64 bytes from 203.109.252.75: icmp_seq=22 ttl=53 time=160.248 ms 64 bytes from 203.109.252.75: icmp_seq=23 ttl=53 time=160.179 ms --- ihug.co.nz ping statistics --- 24 packets transmitted, 24 packets received, 0% packet loss round-trip min/avg/max/stddev = 150.168/233.937/989.994/210.939 ms Apart from 3 outlyers (560, 751, 989), my results would be better than yours. However, I am using dial-up from Brisbane.	vinref (6194)
315068	2005-01-17 08:58:00	Pinging ihug.co.nz [203.109.252.75] with 32 bytes of data: Reply from 203.109.252.75: bytes=32 time=140ms TTL=57 Reply from 203.109.252.75: bytes=32 time=130ms TTL=57 Reply from 203.109.252.75: bytes=32 time=120ms TTL=57 Reply from 203.109.252.75: bytes=32 time=120ms TTL=57 Ping statistics for 203.109.252.75: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 120ms, Maximum = 140ms, Average = 127ms E:\Documents and Settings\PentPro200S>	zqwerty (97)
315069	2005-01-17 09:28:00	Well, thanks for the statistics guys but what I wanted to know was why my ping is gradually crapping out? Maybe someone knows if IHUG or telecom made any changes the adsl line or something? is this something todo with telecom wholesaling the jetstream recently? Anyone else having this annoyance?	ech3lon (5824)
315070	2005-01-17 10:36:00	It's UBS. We've been scr***d. www.nzgames.com	Jester (13)
315071	2005-01-17 11:42:00	It's UBS. We've been scr***d. www.nzgames.com scr***d alrite! well, at least I know wats happenin, this convinces me even further that TELECOM ARE AXIS OF EVIL (or whoever responsible for this) :annoyed:	ech3lon (5824)
1