Pings

[AvengerUK]

Code Select Expand

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

C:\Documents and Settings\Simon>tracert idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    15 ms    15 ms    16 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    16 ms    17 ms    17 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4    18 ms    17 ms    17 ms  redbus-gw.idnet.net [212.69.63.1]
  5    17 ms    17 ms    17 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Simon>

[maxping]

also seems to be a hike in ping times by 10ms after the timeout at 12:05.

Ping to the gateway  is also still 36ms 

Can i ask what you consider to be a ping that is too high for gaming?

In your last 2 posts the highest ping is 37ms are you expecting to get lower than this?

[Adam]

I used to get much lower than 37ms, although I now get around 50-60ms. Not that I really mind, I suspect it could be interleaving.

Just incase anyone is interested;

traceroute to idnetters.co.uk (212.69.36.101), 30 hops max, 40 byte packets
1  <removed> (212.69.xx.xxx)  0.643 ms  0.545 ms  0.612 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  55.196 ms  66.717 ms  55.358 ms
3  telehouse-gw-bb.idnet.net (212.69.63.9)  55.226 ms  55.927 ms  55.132 ms
4  redbus-gw.idnet.net (212.69.63.1)  56.870 ms  55.642 ms  54.647 ms
5  hosting.idnet.net (212.69.36.101)  54.657 ms  55.860 ms  57.021 ms

Adam

[maxping]

I used to get much lower than 37ms, although I now get around 50-60ms. Not that I really mind, I suspect it could be interleaving.

Adam give Miriam a call she has just had a battle with BT over interleaving being put on my line and my pings have gone from a minimum of 50ms to the below.

Pinging www.idnet.net with 32 bytes of data:

Reply from 212.69.36.10 bytes:32 Time:38ms 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
Reply from 212.69.36.10 bytes:32 Time:28ms 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
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:34ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:31ms 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
Reply from 212.69.36.10 bytes:32 Time:28ms 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
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms 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
Reply from 212.69.36.10 bytes:32 Time:26ms 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:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:28ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:27ms TTL:60
Ping statistics for www.idnet.net :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 38ms, Average = 29ms

[AvengerUK]

Over the weekend things where generally ok, however today, its all back again, I also got an email off miriam basically asking me to do the things ive been asked to do so many times, which ive done sooo many times - such as differnt routers? ("have you tried")

Soo...

As of 11:41 - MAC requested

[karvala]

I'm sorry to hear that, but I can entirely understand your frustration.  I think they're making a mistake in the handling of this, by having decided in their own minds that there isn't a problem, and looking round for evidence that this is the case (hence the continued questions about lines and equipment, and running ping tests on a Sunday after having been informed that it's a weekday problem), and ignoring overwhelming evidence that there is.  You're the first casualty, and they'll be more, far more than just the three or four people that they think are currently effected (when in fact it's undoubtedly substantially more than that).  The (mis)handling of this is also damaging their reputation outside, which certainly isn't something I want to see.

Where are you thinking of heading off to?

[AvengerUK]

Im not sure yet - as IDnet really were the best ive had before the ping issue 

Im currently talking to some freinds i have in the ISP industry, who are helping me look into some! Nildram is already out of the equation though = Pipex owned = bad support 

[maxping]

As of 11:41 - MAC requested

Oh no 

Well i guess there comes a time where you have tried everything you can and nothing seems to work,i just hope it does turn out to be something to do with IDNet and not BT or you are going to kick yourself.

Have you decided on a new supplier?

[AvengerUK]

Nope, not yet - although one possible is an enta reseller...!

Not had time to look for one really...currently plowing through pages and pages of quesitons!

http://www.l8nc.com/graph.php?jid=58e61f6e3d3d258ec640ec3f21295d2e - ahh the pain!

[karvala]

Latest results:-

IDNet login using router:
Minimum = 74ms, Maximum = 165ms, Average = 128ms
BT test login using router:
Minimum = 11ms, Maximum = 13ms, Average = 11ms
IDNet login using USB modem:
Minimum = 115ms, Maximum = 164ms, Average = 144ms
BT test login using USB modem:
Minimum = 12ms, Maximum = 19ms, Average = 14ms

Just phoned up and persuaded Tim to verify the results from their end (on the grounds that seeing is believing ), and sure enough he was able to do so (finding some pings over 300ms), and they're going to run some more tests this afternoon, so at least they're still on case.

[equk]

nice

Code Select Expand

traceroute to www.idnet.net (212.69.36.10), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  1.290 ms  0.666 ms  0.653 ms
2  192.168.0.1 (192.168.0.1)  3.190 ms  2.776 ms  3.187 ms
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  147.101 ms  145.147 ms  140.542 ms
4  telehouse-gw-bb.idnet.net (212.69.63.9)  313.264 ms  177.250 ms  318.588 ms
5  redbus-gw.idnet.net (212.69.63.1)  149.165 ms  143.271 ms  139.921 ms
6  www.idnet.net (212.69.36.10)  141.259 ms  138.665 ms  145.675 ms

[maxping]

Yesterday my connection was rock solid and my gaming was fine - (ok it was a bit messy between 15 & 16 but i didnt notice - probably wasnt gaming at the time)




Today i can hardly get the pages to refresh and my pings are a joke - (i have tried the 30 mins shut down trick , it didnt work)

[karvala]

Yes, exactly same here maxping; fine yesterday (being a weekend of course), but today web times really slow, high ping times (very similar looking graph to yours in fact), new session fails to work (except once this morning).  Let's hope the network tests this afternoon reveal something useful, and let's also hope there's no more of this "problem? what problem?" nonsense.

[AvengerUK]

Im still waiting a reply for my MAC request, no doubt ill get a phone call later i suppose  - pings are still very unstable - ie:

One time:

Code Select Expand


  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    24 ms    20 ms    19 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   161 ms   283 ms   247 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4   106 ms   277 ms   327 ms  redbus-gw.idnet.net [212.69.63.1]
  5    23 ms    23 ms    23 ms  www.idnet.net [212.69.36.10]

Trace complete.


And another:

Code Select Expand


  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    90 ms    90 ms    83 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    47 ms    42 ms    41 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4    54 ms    51 ms    48 ms  redbus-gw.idnet.net [212.69.63.1]
  5    39 ms    39 ms    42 ms  www.idnet.net [212.69.36.10]




EDIT:

Code Select Expand

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

C:\Documents and Settings\Simon>tracert idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2   141 ms    96 ms   100 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   197 ms   138 ms   147 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4   191 ms   259 ms   217 ms  redbus-gw.idnet.net [212.69.63.1]
  5   134 ms   123 ms   257 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Simon>

OMG!!

[mrapoc]

you better still keep coming on here after you've left, so you can rejoin once they have  fixed it   

[AvengerUK]

Code Select Expand

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

C:\Documents and Settings\Simon>tracert idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    17 ms    21 ms    24 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    24 ms    19 ms    19 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4    20 ms    18 ms    20 ms  redbus-gw.idnet.net [212.69.63.1]
  5    24 ms    20 ms    26 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Simon>

Router has not resynced/reconnected since the last lot...

[AvengerUK]

And again, not resynced etc, made sure connection was free (nothing else using it) at the time taken....

Code Select Expand

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

C:\Documents and Settings\Simon>tracert idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2   342 ms   330 ms   234 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   189 ms   200 ms   194 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4   214 ms   217 ms   234 ms  redbus-gw.idnet.net [212.69.63.1]
  5   251 ms   410 ms   265 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Simon>tracert idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2   312 ms   312 ms   244 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   183 ms   420 ms   330 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4   218 ms   201 ms   215 ms  redbus-gw.idnet.net [212.69.63.1]
  5   207 ms   222 ms   192 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Simon>tracert idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2   409 ms   324 ms   261 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   320 ms   330 ms   333 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4   367 ms   346 ms   268 ms  redbus-gw.idnet.net [212.69.63.1]
  5   384 ms   387 ms   374 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Simon>tracert idnet.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2   177 ms   174 ms   167 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   210 ms   223 ms   247 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4   262 ms   263 ms   254 ms  redbus-gw.idnet.net [212.69.63.1]
  5   250 ms   247 ms   244 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Simon>

rediculous

[equk]

Ping hasn't been that bad, altho it is higher than normal it was stable.

Code Select Expand

traceroute to www.idnet.net (212.69.36.10), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  1.339 ms  0.672 ms  0.693 ms
2  192.168.0.1 (192.168.0.1)  2.900 ms  2.778 ms  3.138 ms
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  158.621 ms  155.971 ms  148.336 ms
4  telehouse-gw-bb.idnet.net (212.69.63.9)  159.357 ms  147.764 ms  161.866 ms
5  redbus-gw.idnet.net (212.69.63.1)  161.854 ms  163.213 ms  155.984 ms
6  www.idnet.net (212.69.36.10)  158.091 ms  145.008 ms  142.147 ms
until now, yet again 150ms ping to the gateway.

[AvengerUK]

omg - Maxping has just said that a possible reason could be BUISNESSES!

Why did we not think this befoe?!? I think its extremely obvious - pings are worst between 9 and 5 - after that fine! AND only weekdays!

[karvala]

Do I detect the teensiest note of sarcasm in there? 

[browney]

I dont see how as that would mean every one would have a problem

[AvengerUK]

Yes and no, its just that it now seems obvious..where as max is the first person to actually realise it!

[philco]

Not everyone connects using the same bt central pipe or to the same interface. I think i mentioned a few pages back that it could very well be business users overcrowding one of the pipes but i think the guess work is over and it is really upto idnet to find and fix the problem. Its pretty obvious there is a problem and if idnet are to live upto their good name they should be on the case now.

Any chance of some kind of update as to whats happening idnet ? simon ?

[karvala]

Yes and no, its just that it now seems obvious..where as max is the first person to actually realise it!

Huh?  I've been saying for ages that it's *office* hours, i.e. business workers.  Sorry, I thought that was clear. The question is why particular business use should affect only some users, and to a quite extreme extent that varies considerably with time, and sometimes in the very same way for users in completely different locations. It's been quite clear it's business-related in some way; the difficulty is in the details.

[maxping]

My high pings today have tied in with low speeds, at CS's request  i have done speed tests using the BT speed test and the normal ones we all use.

Both tests have given exactly the same results so CS have said its not idnets end its contention at the exchange.

If the BT test was high and the idnet one low they would have something to go on.

As i have said before i do not use my puter much during the day so for me this high ping problem has been a first , I'm not saying i have never had high pings but the 30 mins reset has always cured it before.

CS are still investigating.