and that's the problem Rik

dropping PPP worked fine for me the other day, but is not working now, no matter how many times i try.
So it looks like an imbalance problem is building up but there doesn't now appear to be anything we, as end users, can do anymore..

i, too, am seeing the current speed/ping issues

In reply to:

---

In reply to:

---

So I'm happy to wait (within reason) for them to get things sorted.

---

Latest RSS:

Some users are still experiencing periods of higher latency (pings) than normal whilst we continue to rebalance our network following the new capacity added on Friday. Apologies to those affected, optimisation is taking a little longer than expected but we are making progress and hope to reach optimum performance within the next 24 hours.

---

Thanks Bill, that's more or less what Simon conveyed.

It's just unfortunate that the problem is so apparent for online gamers, especially as Idnet are known as a online gaming friendly ISP.

I have been keeping an eye on things with PingGraph, but it's still all over the place at present.

Edited by Vorlon (Mon 02-Feb-09 19:16:30)

In reply to:

---

Probably to do with costs?

---

That was the message I got.

Well I checked my favourite server on Steam tonight and the ping was anything between 91 - 171, which when I've become used to <40 (and steady) it's a bit of a shock and of course it makes playing online unpractical.

Anyway, I'm probably being too optimistic hoping that things may have progressed and at least improved for me tonight, but I guess I'll have to wait.

Out of all the other servers available on Valve Software's Steam platform, all 14,871 of them available tonight, the lowest ping is 84. Considering that usually the listing starts with servers as low as 20 or so, the current minimum ping through Idnet is very high.

Edited by Vorlon (Mon 02-Feb-09 22:18:14)

In reply to:

---

Probably to do with costs?

---

Or lack of profit. It would allow ISPs to manage bandwidth better, and therefore be able to delay new centrals/new segments a bit longer.

I've just noticed some PPP session drops and some negative comments about it over at Idnetters (i'm not registered there). However the guys at Idnet have been fair and picked a low traffic time - personally I think whilst it's annoying, Idnet have been very reasonable.

The Result and I don't want tempt fate, my connection has gone into Ping Turbo mode. I had to check out in the street to see if Idnet had taken up residence outside my home , it's ultra quick. Of course the customers who have Usb modems will probably be disconnected from Idnet at this late hour and not be contributing to system load.

It's a step in the right direction - so I'm just keeping fingers crossed that all at Idnet who are working on this problem are getting closer to rectifying it. Guy's you can't lose the online gaming Crown!

Things seem to be normalising today. Apart from occasional spikes, my pings are back in range this morning.

Better, but still some way to go:

PING bbc.co.uk (212.58.224.138): 56 data bytes
64 bytes from 212.58.224.138: icmp_seq=0 ttl=122 time=50.884 ms
64 bytes from 212.58.224.138: icmp_seq=1 ttl=122 time=12.973 ms
64 bytes from 212.58.224.138: icmp_seq=2 ttl=122 time=61.764 ms
64 bytes from 212.58.224.138: icmp_seq=3 ttl=122 time=96.257 ms
64 bytes from 212.58.224.138: icmp_seq=4 ttl=122 time=43.804 ms
64 bytes from 212.58.224.138: icmp_seq=5 ttl=122 time=27.231 ms
64 bytes from 212.58.224.138: icmp_seq=6 ttl=122 time=24.903 ms
64 bytes from 212.58.224.138: icmp_seq=7 ttl=122 time=56.005 ms
64 bytes from 212.58.224.138: icmp_seq=8 ttl=122 time=41.896 ms
64 bytes from 212.58.224.138: icmp_seq=9 ttl=122 time=18.546 ms
64 bytes from 212.58.224.138: icmp_seq=10 ttl=122 time=50.880 ms
64 bytes from 212.58.224.138: icmp_seq=11 ttl=122 time=71.324 ms
64 bytes from 212.58.224.138: icmp_seq=12 ttl=122 time=64.498 ms
^C
--- bbc.co.uk ping statistics ---
13 packets transmitted, 13 packets received, 0% packet loss
round-trip min/avg/max/stddev = 12.973/47.767/96.257/22.410 ms

10 second intervals.

After the outage, pings are dire again. I initially thought the outage was to do with part of the rebalancing work, but according to Idnet - not so.

I'm told it may be longer until things are balanced out now, with no doubt todays problems setting the balancing work back?

What does annoy me is that the 0800 number becomes engaged and when you do manage to get back online the status page says everything is wonderful in Idnet land.
I don't receive any emails in advance saying about work/upgrades that have been scheduled, neither (short of the forums) am i advised on what the state of play is - especially at a time like this, when there are ongoing problems.

Download speedsare also poor. I'm down from 7 mbps to a range of 4-1.5 mbps. I phoned IDNet about this and was told the issue is due to a "burst of throughput" following the route issue and that download speeds would return to normal. Time will tell both for pings and speeds...

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 832 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 2666 kbps

Edited by ARD (Tue 03-Feb-09 15:04:05)