Ouchie @ Pings tonight...

Nova · Feb 12, 2007, 19:17:24

Last couple of weeks haven't been too terrific speedwise during peak hours but...

1 1 ms <1 ms 1 ms 192.168.0.1
2 20 ms 19 ms 20 ms telehouse-gw-msdp.idnet.net [212.69.63.41]
3 340 ms 307 ms 307 ms 212.69.63.10
4 279 ms 274 ms 279 ms redbus-gw.idnet.net [212.69.63.1]
5 328 ms 330 ms 350 ms 213.228.201.13
6 258 ms 265 ms 275 ms 72.14.238.244
7 292 ms 285 ms 295 ms 209.85.248.80
8 238 ms 251 ms 252 ms 209.85.248.85
9 281 ms 268 ms 272 ms 72.14.232.141
10 265 ms 306 ms 260 ms 72.14.233.77
11 272 ms 290 ms 262 ms 66.249.94.46
12 263 ms 234 ms 252 ms ug-in-f104.google.com [66.249.93.104]

Trace complete.

*wince*

Nova

DorsetBoy · Feb 12, 2007, 19:22:50

Mmmmmm, speeds have been a bit erratic all day today,just checked pings and mine are all @ 300 at present.

maxping · Feb 12, 2007, 19:26:25

Nova try - http://www.idnetters.co.uk/forums/index.php/topic,1236.0.html

Nova · Feb 12, 2007, 19:44:40

Done, but it's still messy, World of Warcraft is currently waving between 300-500 , compared to last month when over 200 would have been a rare event. Something tells me this new capacity will be a deeply welcome thing.

Nova

Desaan · Feb 12, 2007, 19:51:54

Yeah having the same issues atm, I know hammering tracerts isn't proof of an issue but when I'm getting such erratic results as this..... (done 10secs apart)

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

D:\>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 2752 ms 608 ms 140 ms telehouse-gw-msdp.idnet.net [212.69.63.41]
2 124 ms 140 ms 140 ms 212.69.63.10
3 77 ms 46 ms 62 ms redbus-gw.idnet.net [212.69.63.1]
4 93 ms 93 ms 77 ms www.idnet.net [212.69.36.10]

Trace complete.

D:\>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 70 ms 46 ms 62 ms telehouse-gw-msdp.idnet.net [212.69.63.41]
2 124 ms 109 ms 124 ms 212.69.63.10
3 187 ms 187 ms 187 ms redbus-gw.idnet.net [212.69.63.1]
4 233 ms 218 ms 218 ms www.idnet.net [212.69.36.10]

Trace complete.

D:\>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 524 ms 124 ms 827 ms telehouse-gw-msdp.idnet.net [212.69.63.41]
2 202 ms 187 ms 202 ms 212.69.63.10
3 218 ms 218 ms 218 ms redbus-gw.idnet.net [212.69.63.1]
4 234 ms 218 ms 218 ms www.idnet.net [212.69.36.10]

Trace complete.

D:\>

Is this likely to be a Max DSL only issue? If so please give me a static 2mb line.....not long signed up with IDNet, so far not impressed....

Nova · Feb 12, 2007, 19:57:41

I'm on a fixed 2mb Line, so my thesis is that it's not BT's network itself, but likely the congestion that has been mentioned at IDNet's side, which -should- (touch wood) be resolved with the extra capacity being installed this month I believe?

Lance · Feb 12, 2007, 19:59:59

Indeed, the new capacity is supposed to be in before the end of the month.

Nova · Feb 12, 2007, 20:54:43

update : Pings seem more coherent now at around 21:00 , this means that between 18:00 and 21:00 (highest peak usage) there is a severe increase in latency (this is something I've had every day, during the night my pings to IDnet are almost LAN level speed). This really looks like a capacity issue, or simply the fact now the demand is too much to safely load balance?

Example traceroute at 20:58

Tracing route to www.l.google.com [66.249.93.104]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.0.1
2 18 ms 19 ms 20 ms telehouse-gw-msdp.idnet.net [212.69.63.41]
3 87 ms 92 ms 71 ms 212.69.63.10
4 71 ms 74 ms 69 ms redbus-gw.idnet.net [212.69.63.1]
5 67 ms 71 ms 89 ms 213.228.201.13
6 58 ms 51 ms 51 ms 72.14.238.244
7 63 ms 65 ms 63 ms 209.85.248.80
8 31 ms 41 ms 52 ms 209.85.248.85
9 42 ms 41 ms 57 ms 72.14.232.141
10 77 ms 94 ms 119 ms 72.14.233.77
11 90 ms 83 ms 81 ms 216.239.47.229
12 62 ms 53 ms 52 ms ug-in-f104.google.com [66.249.93.104]

Trace complete.

Nova

mrapoc · Feb 12, 2007, 22:12:53

Gaming has been poor tonight to say the least - even after restarteing router etc. i know the drill

Please not again!

maxping · Feb 13, 2007, 00:56:57

Opened ASE at approx 10 p.m and pings were low and gaming fine.
I rarely play before 10 so don't know how peak time effects it.

Rik · Feb 13, 2007, 00:59:20

Just ran PingPlotter here, pings to the sites I usually test are about 10mS greater than usual, eg 38 rather than 28.

maxping · Feb 13, 2007, 01:01:09

This is about the norm for me.

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60

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

Nova · Feb 13, 2007, 01:04:39

That's the norm for me now... WoW is sillyfast - 44ms

During peak hours it's most -definitely- not up to scratch. 18:00-21:00 is no go right now if you're a gamer.

Nova

Rik · Feb 13, 2007, 01:07:24

Quote from: maxping on Feb 13, 2007, 01:01:09
This is about the norm for me.

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60

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

I'm a bit slower, Max - put it down to age.

Pinging 212.69.36.10 with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=32ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60

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

I do have interleaving ON.

maxping · Feb 13, 2007, 01:21:06

Quote from: rikbean on Feb 13, 2007, 01:07:24

I do have interleaving ON.

I used to but Miriam got BT to turn it off, my pings dropped approx 20ms.

Rik · Feb 13, 2007, 01:22:57

In which case, I seem to be doing better than you, relatively. Perhaps it's because I'm not too far up the road from IDNet Towers?

CreamyGoodness · Feb 13, 2007, 10:19:30

Unfortunately, it's between 7 and 10 in the evenings that league or practice matches are scheduled for a lot of games. My match last night was humiliating. It does seem that after about 11, pings get lovely and low.

Don't know anything about these "centrals", but would be interested to know how many users one can supply. Does IDNet only have one at the moment and is therefore doubling capacity this month, or will it only deliver, say, a 20% improvement? With pings consistently above 200ms at some times of day, it would seem to me that the current capability is vastly overstrecthed.

I can't help feeling there's a market out there for a gamer's-specific broadband package where gaming traffic gets prioritised for latency. Personnally, I only need about 2GB a month download limit and a 1MB connection. I would happily give away the spare 7MB of my bandwidth in exchange for ping. (Probably just showing my ignorance of how these things work, heheh).

Creamy.

cavillas · Feb 13, 2007, 12:11:36

I beleive that IDnet have 3 centrals and with the new one that will make 4. I'm sure I saw it somwhere either here or IDnet site.

Rik · Feb 13, 2007, 12:36:24

Or possibly on TB, they often show the number of centrals an ISP has.

Glenn · Feb 13, 2007, 17:09:27

I game, but not FPS, I use rFactor which is a racing game, a damned fine one too. It is very tolerant of high pings, no warping is apparent with the cars when the pings are up around 250ms. The more important factor is the connection quality, as the server relays the car position on track to all the clients.

Nova · Feb 13, 2007, 18:00:53

Warcraft is a bit odd, you need a stable -and- fairly latency free connection, particularly for healing and tanking clases where reaction time is a key factor. Right now pings look good but I can "feel" a choppiness in the line which is usually associated with overload, intuition being the finely tuned thing it is.

Nova

maxping · Feb 13, 2007, 18:40:08

I think at the moment its a case of connect try pinging idnet if its bad do the speedtest@speedtest trick and repeat until you get good pings.
My connection was poor at this time last night yet today its fine.

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60

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

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60

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

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60

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

CreamyGoodness · Feb 13, 2007, 18:57:59

Same here actually. Right now ping's looking nice:

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60

Got a match in an hour, let's hope it lasts

And I've just checked my router, this is with interleaving on. Maybe sub 10ms pings may be possible........

Desaan · Feb 13, 2007, 19:12:37

My results are somewhat.....less consistent

Pinging idnet.com [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=49ms TTL=61

Reply from 212.69.36.10: bytes=32 time=46ms TTL=61

Reply from 212.69.36.10: bytes=32 time=62ms TTL=61

Reply from 212.69.36.10: bytes=32 time=46ms TTL=61

Ping statistics for 212.69.36.10:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 46ms, Maximum = 62ms, Average = 50ms

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

D:\>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 316 ms 577 ms 62 ms telehouse-gw-msdp.idnet.net [212.69.63.41]
2 62 ms 62 ms 46 ms 212.69.63.10
3 77 ms 60 ms 62 ms redbus-gw.idnet.net [212.69.63.1]
4 92 ms 93 ms 77 ms www.idnet.net [212.69.36.10]

Trace complete.

D:\>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 3781 ms 1249 ms 187 ms telehouse-gw-msdp.idnet.net [212.69.63.41]
2 62 ms 77 ms 62 ms 212.69.63.10
3 46 ms 62 ms 46 ms redbus-gw.idnet.net [212.69.63.1]
4 93 ms 93 ms 77 ms www.idnet.net [212.69.36.10]

Trace complete.

D:\>

crazy stuff, tried the btspeedtest login but doesnt help at all

maxping · Feb 13, 2007, 19:19:12

Give it another try ,it took me 3 tries once but it worked in the end.