In reply to:

---

Pings don't normally bother me, I only do them if someone explicitly asks for them.

But when they're this bad for this long, something's amiss somewhere...

---

I agree,

I've been with Idnet for awhile now and tend to play on the same European server, plus occasionally other UK servers, so i know what the average range of pings (for me) is.

Unfortunately at this moment of time my favourite TF2 server is averaging 170ms (normally sub 50ms) and the server admin has set the limit to 150ms - so it's not basically usable for me this evening.

All I can say is that things sometimes go awry with IDNet, just as they do with any other ISP (visited the Entanet forum recently? ).

But unlike many others, they fix it as quick as they can...

Tonight's re-balancing work seems to have been successful, we'll be monitoring closely to prevent a recurrence.
Simon

Cheers Simon.

It's a lot better, but still not down to the consistent 12-13ms I usually get to the beeb.

Averaging about 30ms at a guess, and still erratic- down to 13ms and up to 120-odd.

Apart from an occasional flier, seems to be pretty much back to normal now

I did have a quick look at the Steam servers (full listing) and now at 00:00hrs the minimum latency is 73ms, which is better, but not really as good as it always was. I assume it's not fully recified as of yet?

In reply to:

---

Tonight's re-balancing work seems to have been successful, we'll be monitoring closely to prevent a recurrence.
Simon

---

Seems to be back to normal here but it is early in the morning.


Pinging jolt.co.uk [84.234.17.86] with 32 bytes of data:

Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=24ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=24ms TTL=124
Reply from 84.234.17.86: bytes=32 time=24ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=24ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=27ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=24ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=29ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=22ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86: bytes=32 time=24ms TTL=124
Reply from 84.234.17.86: bytes=32 time=23ms TTL=124
Reply from 84.234.17.86:

Not bad enough here to complain, but not quite back to normal. Average (to bbc.co.uk) is about 15-16msec instead of 12-13msec, with occasional fliers up to several hundred, which I've never seen before.

Though to be fair, I suppose the BBC website might be a touch busy this morning

Have you guys gone over to IPSC?

TBH I don't even know what IPSC is .

The Status Notification from last week said:

Our new Central (into BT's 20th Century Network) and the new 1Gbps Host Link into the 21st Century Network (for up to 24 Mbps ADSL2+ services) are scheduled to go live tomorrow.

Whether that's connected to the increased pings last night I have no idea, I leave the gory innards of IDNet's network to those who know what they're doing