Ouchie @ Pings tonight...

[Nova]

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]

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

[maxping]

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

[Nova]

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]

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]

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]

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

[Nova]

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]

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

Please not again!

[maxping]

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]

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

[maxping]

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]

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]

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]

I do have interleaving ON.

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

[Rik]

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]

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]

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]

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

[Glenn]

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]

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]

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]

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]

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]

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

[neocr0n]

Some bad pings for me again tonight.  Is this accross IDnet because I've been having problems in general anyway so can anyone confirm they are also having latency issues tonight?

Thanks,

Jonathan.

[CreamyGoodness]

Yep, pings bad here now too    More like what I've come to expect.....

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

Reply from 212.69.36.10: bytes=32 time=148ms TTL=60
Reply from 212.69.36.10: bytes=32 time=130ms TTL=60
Reply from 212.69.36.10: bytes=32 time=131ms TTL=60
Reply from 212.69.36.10: bytes=32 time=154ms TTL=60

Creamy.

[Nova]

And here comes the lag *mutter*, will get pings and traceroutes once free.

Nova

[maxping]

Any news from IDNet on the new pipe?

[Nova]

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

  1     *        *        *     Request timed out. <--- ignore this, my router is set not to respond to pings on WAN
  2   111 ms   125 ms   153 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3   147 ms   172 ms   161 ms  212.69.63.10
  4   203 ms   157 ms   184 ms  redbus-gw.idnet.net [212.69.63.1]
  5   170 ms   155 ms   166 ms  213.228.201.13
  6   154 ms   135 ms   159 ms  72.14.238.244
  7   174 ms   185 ms   192 ms  209.85.248.80
  8   175 ms   172 ms   151 ms  209.85.248.85
  9   173 ms   174 ms   176 ms  64.233.175.246
10   148 ms   187 ms   216 ms  72.14.233.81
11   196 ms   184 ms   184 ms  216.239.47.229
12   209 ms   195 ms   189 ms  66.249.93.147

Trace complete.

[RostokMcSpoons]

I'm getting 250ms pings at the moment, and I'm supposed to be playing in a clan match in 20 minutes   

I've repeatedly tried logging to the BT speedtest / connection test sites (for the alleged 'fix'), but none of them will let me connect (error 720 - 'you may need to change your connection settings')

At the moment I'm definitely *not* a happy bunny... halfway through the month and still no news of when it's getting fixed.

[LuMpY]

This is getting to a pain now.

I can no longer play games at peak time, which happens to be when i want to play.

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

Reply from 82.133.85.65: bytes=32 time=199ms TTL=57
Reply from 82.133.85.65: bytes=32 time=223ms TTL=57
Reply from 82.133.85.65: bytes=32 time=229ms TTL=57
Reply from 82.133.85.65: bytes=32 time=214ms TTL=57

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

Earlier today it was 19/20ms, i've already got interleaving turned off and still this hasnt helped. Rebooting doesnt help.

Sky broadband is £15 cheaper per month without a cap, it is know to have higher than usual pings, but not anywhere near 216ms.

Is there going to be a fix anytime soon?

[Desaan]

Not been with IDNet long, after ditching my last IP due to email and account realated issues at least they where stable and performed well (Ace Internet)

Since getting my connection with IDNet its been just woefully inadiquate, trying to play online from early to late evening is just pathetic.  Latency bouncing and skyrocketing all over the place 

I'll give it a while longer but I'm not one for paying for something I'm not getting.

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



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

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

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

Reply from 212.69.36.10: bytes=32 time=249ms 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 = 249ms, Maximum = 295ms, Average = 276ms



Pinging bbc.com [212.58.227.77] with 32 bytes of data:



Reply from 212.58.227.77: bytes=32 time=299ms TTL=249

Reply from 212.58.227.77: bytes=32 time=281ms TTL=249

Reply from 212.58.227.77: bytes=32 time=296ms TTL=249

Reply from 212.58.227.77: bytes=32 time=249ms TTL=249



Ping statistics for 212.58.227.77:

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

Approximate round trip times in milli-seconds:

    Minimum = 249ms, Maximum = 299ms, Average = 281ms

[maxping]

We are going to suffer with high pings until the new capacity comes on-line this month,i have found its a bit of a lucky dip sometimes i connect and they are low sometimes high,if i use the speedtest@speedtest log in (see thread at top of list in main help menu) i can get lower pings but not always.
I know its a total pain in the a**e when you want to play and the pings stop you but as Ive said we should be sorted soon and we should be happy gamers again.

[maxping]

For those new to the forums IDNet ordered more capacity from BT 2 months ago to keep up with demand ,unfortunately it takes BT 3 months to supply it so this month it will happen. 

[RostokMcSpoons]

maxping, that speedtest thing does not work for me - it won't let me connect.  Are there any alternatives (or am I just being a muppet in some way?)

[stevie0573]

Hi guys been awhile

Ive been having a few problems with pings just lately (OMG gamer :p) thanx max for the heads up on what is happening.

steve

[jakarra]

yehh well thats great at least I know why im getting kicked from my clans server but for gods sake u dont expect me to pay full price when I am not reciving 100% service ?? I came to idnet because they boasted the catererd for gamers, lately my ping has been horendus and my d/l rate has been halved

[Desaan]

So basically Max, what we have atm is an oversubcribed ISP happy to to keep reeling customers that they cant keep happy?

If IDNet are over capacity and have ordered more 'pipes' from BT, should this not a severe misdirection from a sales point of view?  Nowhere on their site do I find anything about new capacity opening up this month to aleviate current congestion.

Can't help but feel slightly aggrieved at the moment

[neocr0n]

Can't really "confirm" anything but I did speak to Simon on the phone only a few days ago and he mentioned again new capacity opening up shortly.

However he also said IDnet rarely reaches its limit on the network and when it does its only for a short period of time like 15 minutes etc.  So not sure why this horrible latency problem continues for a few hours at the least

[Nova]

This is after leaving the router "Cold" (unpowered) for 40 mins. Now - download and upload speeds are fairly decent, even for peaktime usage. The Latency figure is the cause for alarm, which leaves me at a loss. I am on a fixed 2 megabit package so to see 1.6 ish isn't bad at all for this time of day.

Nova

[Jobe]

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

Reply from 212.69.36.10: bytes=32 time=197ms TTL=60
Reply from 212.69.36.10: bytes=32 time=211ms TTL=60
Reply from 212.69.36.10: bytes=32 time=192ms TTL=60
Reply from 212.69.36.10: bytes=32 time=249ms 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 = 192ms, Maximum = 249ms, Average = 212ms


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

Reply from 212.69.36.10: bytes=32 time=250ms TTL=60
Reply from 212.69.36.10: bytes=32 time=148ms TTL=60
Reply from 212.69.36.10: bytes=32 time=184ms TTL=60
Reply from 212.69.36.10: bytes=32 time=181ms 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 = 148ms, Maximum = 250ms, Average = 190ms


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

Reply from 212.69.36.10: bytes=32 time=239ms TTL=60
Reply from 212.69.36.10: bytes=32 time=221ms TTL=60
Reply from 212.69.36.10: bytes=32 time=221ms TTL=60
Reply from 212.69.36.10: bytes=32 time=195ms 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 = 195ms, Maximum = 239ms, Average = 219ms


Grrr, been like this most of the evening from 7pm ish

[CreamyGoodness]

From the http://www.idnet.net/broadband/ home page:

"No contention on our network is achieved by not oversubscribing our broadband services and ensuring that bandwidth investment exceeds customer demand. This means that our goals of the highest performance and reliability can be maintained."

[PuncH]

my xbox live gaming has been a bit iffy tonight too. games of pro evo would start off being rather laggy and then settle down after 30 seconds or so.

'tis the first time i've ever had cause to whinge a little about idnet and i've been with them for over a year. the nice thing is though, i know they're sorting it.

also, my exchange capacity is at red acording to the plusnet checker so that might not be helping either!

I just done a speedtest too...wasn't great!



Bearing in mind I've done speedtests at 9.30pm before on that site and got 6558 kb/s download (my best ever score)

[Desaan]

Can't really "confirm" anything but I did speak to Simon on the phone only a few days ago and he mentioned again new capacity opening up shortly.

However he also said IDnet rarely reaches its limit on the network and when it does its only for a short period of time like 15 minutes etc.  So not sure why this horrible latency problem continues for a few hours at the least

Well judging from the amount of tracerts and ping plots coming in from people all over the country, different connection speeds etc - It's very clear that the IDNet network if not always reaching full capacity is suffering from very heavy traffic IE over congested - over subscribed.

High rises in latency at peak times would clearly indicate that because after 11pm it very quickly drops back close to being what it should be.

[maxping]

maxping, that speedtest thing does not work for me - it won't let me connect.  Are there any alternatives (or am I just being a muppet in some way?)

You can only use the speed test it wont let you surf.
You do not need to run the test once its on screen you can go back and use your idnet log in .
In theory it should work but doesn't always.
You can also turn your router off for 30 mins its been known to work.

[maxping]

yehh well thats great at least I know why im getting kicked from my clans server but for gods sake u dont expect me to pay full price when I am not reciving 100% service ??

IDNet have been very honest about the situation and posted here in the forums that they had ordered more capacity and said BT couldn't supply it until this month,they also are trying to move people around to try to balance users connections.
If you are not happy with the service and are to impatient you are on a 1 month contract you can always leave.
No one minds people coming here to get things off their chests and most of us have at some time,you now know why the pings are high so its up to you.
Just to add they are not always high ,tonight is the first time i have had high pings i cannot fix with the BT log in so maybe theres a reason. 

I came to idnet because they boasted the catererd for gamers, lately my ping has been horendus and my d/l rate has been halved

Erm where does it say they "cater for gamers" ?
As Ive already posted they are having capacity issues , they have set the wheels in motion to sort the problem its now down to BT.


Just checked and they are back to normal

[PuncH]

Just done another speed test now all the little kiddies have gone to bed...much more like it



Shame I'm off to bed myself now!

[RostokMcSpoons]

You can only use the speed test it wont let you surf.
You do not need to run the test once its on screen you can go back and use your idnet log in .
In theory it should work but doesn't always.
You can also turn your router off for 30 mins its been known to work.

Maxping, you misunderstand - it won't accept the connection.  I get the 0720 error message from the speedtouch dialog.

http://www.brooker.eclipse.co.uk/Web/error.jpg

[maxping]

Strange ive never seen that before 

[Nova]

mrrr... forums bugging... anyways... an official word could be handy. This feels like something on top of just congestion.

[maxping]

mrrr... forums bugging... anyways... an official word could be handy. This feels like something on top of just congestion.

Have you seen the post from Simon IDNet's owner?

We have seen that the traffic through our Centrals has become unbalanced
recently. This is particularly apparent during the highest peak hours of 8pm
to 10pm. We are working at re-balancing the traffic.

We have more capacity due to come online at the end of February which will
alleviate the problem. The sudden increase in traffic has been due to an
unforeseen influx of customers recently.

Apologies to those affected.
Regards
Simon

[Nova]

Use the editing trick again:

Yes I read the post, I am capable of comprehension. Now read the second sentence of mine since that is rather important to put into context.

Thank you.

[Rik]

If you want more information than has been posted, why not give CS a ring later today? I'm sure they will give you as much information/explanation as they can for any current issues, eg the smtp server had problems last night - a call to the out of hours number elicited a fix and a call from Tim to the affected user.

As users, we can only repeat what we have been told before you joined. There have been no updates since to my knowledge.

[Nova]

Yea, sorry if I seemed a little off with the last post. I do make an effort not to take up time of people who I know are working to provide the service we use (IDnet) and largely prefer information in public places if there needs to be updates since having done techie I can promise:

50 people all ringing with the same question a single forum post can answer, it's not fun for paracetamol usage ;-) It's easier to have an official post or thread of sorts (see warcrafts realm status forum) where everyone can be pointed at so you just say "RTFF" as opposed to explaining to every single person individually.

(having to near blankpost and then edit in the replies, wi-erd). My point is this: The latency seems to clear up a little too fast to just be congestion, there is a near measurable 3 hour window where it's "predictably poor" and then 21 hours where it's insanely fast.

Nova

[Jobe]

From the http://www.idnet.net/broadband/ home page:

"No contention on our network is achieved by not oversubscribing our broadband services and ensuring that bandwidth investment exceeds customer demand. This means that our goals of the highest performance and reliability can be maintained."

This is exactly what I was told on the phone before I signed up with IDNET, as I had the same problem coming from another ISP. It was this alone that got me here in the first place, but I was told by someone here (As If I was lieing) that they would of never told me that on the phone hehe.

Thanks for finding that quote CG  

Still like most here there is nothing that can be done until the end of the month

If nothing changes then it's MAC time for me I'm affriad. Well it should help out with the contention problem at least with one less to worry about hehe..

[Rik]

Yea, sorry if I seemed a little off with the last post.

That's OK, I understand your frustration. I take your point about the use of this board (or TB) to explain service problems. I actually think it would be best if it were on the status page of the IDNet website. My reasoning is that not all customers will use forums, but they do all have easy access to the website.

I would guess that the problem with information flow is that the company is relatively small, so it's part of someone's job, rather than having one or more people dedicated to communicating. It's the old 'swamps and alligators' issue.

[Rik]

This is exactly what I was told on the phone before I signed up with IDNET, as I had the same problem coming from another ISP.

Afaik, the lack of contention is still company policy. The problem stems from two issues. Normally, IDNet pre-order extra capacity as they see their need growing. Because BT has a 3-month lead time, it has to be carefully planned - ordering too early just costs the company money, ordering too late causes the sort of problems you are complaining of. On the basis of their normal growth, I understand that IDNet ordered a new central in November.

Unfortunately, between November and January (and possibly continuing), there was an unexpected and large influx of new customers - refugees from other ISPs for various reasons. That 'surge' was unpredictable, and it threw out IDNet's planning. Because you can't budge BT, even with a couple of sticks of dynamite, IDNet couldn't get the extra central online any earlier, and this resulted in the current capacity issues. They have done their best to manage the resources they have and, for most people, the problems are limited to a few hours a day - if they notice them at all.

Sadly, of course, those are probably the few hours a day that matter most to you.

[maxping]

Unfortunately, between November and January (and possibly continuing), there was an unexpected and large influx of new customers - refugees from other ISPs for various reasons. That 'surge' was unpredictable, and it threw out IDNet's planning. Because you can't budge BT, even with a couple of sticks of dynamite, IDNet couldn't get the extra central online any earlier, and this resulted in the current capacity issues. They have done their best to manage the resources they have and, for most people, the problems are limited to a few hours a day - if they notice them at all.

Sadly, of course, those are probably the few hours a day that matter most to you.

Well put mate

Pings tonight are fine @ 6 p.m.

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=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=44ms TTL=60
Reply from 212.69.36.10: bytes=32 time=48ms 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 = 48ms, Average = 35ms

[Rik]

I got 29/32/29, but then I always was an odd shape.

[maxping]

Use the editing trick again:

Yes I read the post, I am capable of comprehension.

Its the speedtest trick not editing trick 

[Nova]

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

Reply from 212.69.36.10: bytes=32 time=22ms TTL=60
Reply from 212.69.36.10: bytes=32 time=19ms TTL=60
Reply from 212.69.36.10: bytes=32 time=18ms 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 = 18ms, Maximum = 26ms, Average = 21ms

Just as control data, this is what it looks like from my end at 18:05

[Rik]

I just hope you don't expect me to type your user name ever!

[Inactive]

Yay! Pings seem normal tonight

Welcome erm er .............

Well welcome aboard

[Rik]

I think it's his WPA key.

[maxping]

I think it's his WPA key.

[RostokMcSpoons]

Yay! Pings seem normal tonight

.... Valentine's night... lots of geeks do have girlfriends after all

Tonight is going to be a different matter I fear - I'm already up to 70ms and expecting to see it 'unplayable' by in an hour or two   

[Nova]

I'm also seeing MASSIVE packetloss going towards Telia's network, 20% and up. Ping internal to IDNet is however at 20 msec, but the moment it gets toward google - add another 100 msec. The good news is that the new central comes in over this/the next week.

I might see if there's any way to bribe to be moved to the new central *grin*

Nova

[neocr0n]

Well did the btspeedtester trick at 7:40 and all was well for ooo lets see 30 minutes or just over.  Latency has shot up to over 100 now

[RostokMcSpoons]

Actually, I've been lucky... it peaked at 150ms for a few minutes, but I decided to play anyway and it went straight back down to 40ms, and it's still looking ok.

So I've got no complaints tonight.