Ouchie @ Pings tonight...

[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.