Ping times Jan 28 onwards

[JB]

I thought I might submit a ticket but was afraid of a frosty response.

[Glenn]

You should snow they would treat your ticket fairly, they are most likely getting a flurry of them anyway

[Rik]

Quite the opposite, JB, you'd get a warm greeting and red hot service.

[Rik]

You should snow they would treat your ticket fairly

It must be catching.

[Glenn]

Look again

[JB]

I'll drift over to IDNet later and plough my way throught the ticket system.

[Glenn]

 

[Rik]

I used to run a firewall called BlackIce - shame they dropped it really.

[Steve]

I'll drift over to IDNet later and plough my way throught the ticket system.

What? And tell them your connection has gone all flaky

[Rik]

I see you lot are really crystallising your thinking this morning.

[esh]

Yeah it's getting worse again. Here's my current gw5 plots.


Pretty obvious where the troubles began. Note each data point is an average of 144 measurements.


The raw data of the past week (each point is 10 minutes apart). Fairly shambles right now as you can compare directly to what it was like before.

At least the thing is stable, that's what matters most to me.

[Rik]

Try dropping your PPP session and re-connecting.

[esh]

I'll power the main router off for 40 minutes tonight out-of-hours and then start it up again.

[Lance]

Here are my latest graphs, largely settled now but earlier on was a bit dodgy.

[attachment deleted by admin]

[Steve]

I've had a reply from Simon who states "that they are having problems with their pipes into BT becoming unbalanced.This meant that some routes became congested which has caused performance problems. We are monitoring closely in order to alleviate the problems."

Amazing how implementing extra capacity can lead to congestion. However they've sorted it before

[Rik]

The last I heard was that they are manually forcing people onto different pipes as they reconnect. I'm surprised that the BT system isn't more efficient at doing this automatically.

[Lance]

I don't think BT and their systems are efficient at doing anything. 

[Rik]

Neither does Simon.

[neocr0n]

I don't know where the fault lies today, with the weather and everything but my latency is still all over the place today.

Between 80-180

no online gaming for me.

[Rik]

Have you tried dropping PPP and re-connecting?

[Steve]

I tried dropping PPP but came back just as bad most pings are now in three figures again

[Rik]

IDNet were forcing people onto different pipes when they reconnected. This is all supposed to be done automatically by BT's system, but it's just not happening.

[Rik]

Update from IDNet:

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.

[Aaron]

Unless I'm mistaken, most of the replies on bad pings are related to gw5, I've only just had a look at my ping now since website loading was somewhat slow and it's going through gw2:

C:\Documents and Settings\Aaron>tracert www.multiplay.co.uk

Tracing route to core1.multiplay.co.uk [85.236.96.22]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2   526 ms   131 ms   170 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   155 ms   165 ms   151 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   153 ms   148 ms   145 ms  lonap2.enta.net [193.203.5.135]
  5   169 ms   138 ms   118 ms  te4-4.telehouse-east.core.enta.net [87.127.236.97]
  6   103 ms   109 ms   122 ms  te5-4.global-switch.core.enta.net [87.127.236.82]
  7    88 ms    92 ms    98 ms  te1-1.interxion.core.enta.net [87.127.236.86]
  8   155 ms   143 ms   135 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  9   177 ms   164 ms   146 ms  po0-1-651-cr.ixnlon.as35028.net [85.236.110.11]
10   110 ms   111 ms   120 ms  www1.multiplay.co.uk [85.236.96.22]

Trace complete.

C:\Documents and Settings\Aaron>tracert www.idnet.co.uk

Tracing route to www.idnet.co.uk [212.69.36.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2   101 ms   117 ms   125 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   129 ms   143 ms   135 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   110 ms   103 ms   116 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   151 ms   143 ms    74 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    72 ms    72 ms    83 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Rik]

I'm on DSL5, Aaron, but my pings are erratic, occasionally down in the low 20s as I'd expect, but at other times they lurch up into the 150s. Hopefully, it will all settle down in the next day or so.