Lost connection

Rik · Oct 11, 2010, 16:25:06

Did you want the half back?

It makes you wonder if the circuit was misconfigured in the first place.

Technical Ben · Oct 11, 2010, 16:32:34

Quote from: Rik on Oct 11, 2010, 16:25:06
Did you want the half back?

It makes you wonder if the circuit was misconfigured in the first place.

Or if everyone is to scared to try reconnecting?

Rik · Oct 11, 2010, 16:34:44

Could be.

Conrad · Oct 11, 2010, 17:43:45

I thought there was a 4 hour SLA on MSOs? Maybe I'm wrong. I'm certain that BT provide ETRs via ECO, so it would have been nice to hear a better update on the cust-svc number. The only reason I can think of for such a complete cease of service would be non-payment of a bill

Idnet aren't in trouble are they?

Rik · Oct 11, 2010, 17:50:14

No, they're not in trouble. Currently, they are waiting for an explanation from BT of what happened, and what will be done to ensure that it can't happen again. The delay was caused by BT's insistence on sending out two engineers, who took three hours to arrive when the fault clearly wasn't a physical issue, ie IDNet could see all the lines were 'up'. Simon then had to persuade the BT helpline in California to get their fingers out and reinstate the configuration.

cavillas · Oct 11, 2010, 17:55:04

BT shoyuld'nt have a helpline in California, they should all be in this countyr to help with our employment and debt problems.

Rik · Oct 11, 2010, 17:56:27

It's better than Mumbai, Alf.

Technical Ben · Oct 11, 2010, 18:05:16

Quote from: Rik on Oct 11, 2010, 17:50:14
... the BT helpline in California...

Well, I hate to be pessimistic, or judgemental, but...

They were probably trying to get some surf time.

Rik · Oct 11, 2010, 18:10:54

Now surf and turf I could understand.

pctech · Oct 11, 2010, 18:30:14

Quote from: Technical Ben on Oct 11, 2010, 18:05:16
Well, I hate to be pessimistic, or judgemental, but...

They were probably trying to get some surf time.

Maybe they were told the fibres needed cleaning.

Rik · Oct 11, 2010, 18:34:54

I think micro-fibre got lost in translation...

zappaDPJ · Oct 11, 2010, 18:51:19

Quote from: Rik on Oct 11, 2010, 15:51:37
Useful to know, Zap. Have you told support about the router?

No Rik but if speeds are consistently higher I certainly will do.

Kareha · Oct 11, 2010, 18:54:21

Seems that routing to World of Warcraft may have gone to pot, prior to last nights outage I was getting pings of around 45-50ms, tonight logged on to raid and Im currently sitting at 363ms, rising to near enough 500ms. In contrast I am also in the beta for the new expansion and that server is located in California, and Im currently getting between 185 and 233ms. My server for the live WoW system is located in France.

Here is a tracert to my server showing yet again that once it jumps onto Telia it goes pear shaped, everything was fine until last nights outage:

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 27 ms 26 ms 26 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 25 ms 26 ms 26 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 25 ms 30 ms 28 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148
05]
5 26 ms 26 ms 26 ms te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
38]
6 120 ms 66 ms 26 ms te4-3.ccr01.lon01.atlas.cogentco.com [130.117.1.
7]
7 27 ms 26 ms 120 ms te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.
5]
8 138 ms 138 ms 138 ms ldn-b4-link.telia.net [213.248.70.237]
9 141 ms 138 ms 139 ms ldn-bb1-link.telia.net [80.91.249.77]
0 146 ms 186 ms 146 ms prs-bb2-link.telia.net [80.91.247.240]
1 160 ms 156 ms 156 ms ffm-bb2-link.telia.net [80.91.246.184]

Rik · Oct 11, 2010, 18:58:31

It should only be coincidence. Let support have the trace (preferably two or three) and they can check the routing.

My trace shows:

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

C:\WINDOWS>tracert 80.91.246.184

Tracing route to ffm-bb2-link.telia.net [80.91.246.184]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.254
2 13 ms 13 ms 13 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 14 ms 15 ms 11 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 12 ms 11 ms 13 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
5 12 ms 15 ms 14 ms te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50.138]
6 15 ms 15 ms 11 ms te4-3.ccr01.lon01.atlas.cogentco.com [130.117.1.217]
7 12 ms 11 ms 11 ms te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.225]
8 124 ms 124 ms 125 ms ldn-b4-link.telia.net [213.248.70.237]
9 127 ms 125 ms 126 ms ldn-bb2-link.telia.net [80.91.254.21]
10 133 ms 132 ms 131 ms prs-bb2-link.telia.net [80.91.247.240]
11 165 ms 145 ms 144 ms ffm-bb2-link.telia.net [80.91.246.184]

which suggests to me you may have interleaving on.

Kareha · Oct 11, 2010, 19:02:36

I'll do a couple more, and Interleaving is definately off, my router is showing it as Fast:

--------------------------- ATU-R Info (annex A) ----------------------------
Running Mode : G.DMT State : SHOWTIME
DS Actual Rate : 4256000 bps US Actual Rate : 832000 bps
DS maximum Rate : 4256000 bps US maximum Rate : 832000 bps
DS Path Mode : Fast US Path Mode : Fast
NE Current Attenuation : 33.0 dB Cur SNR Margin : 12.0 dB
DS actual PSDM(C) : 00000000 US actual PSDM(R) : 00000000
ADSL Firmware Version : E.38.2.23
-------------------------------- ATU-C Info ---------------------------------

Also one of my guildmates who is also with IDNet is having the exact same issue as me, very high ping to our server.

Rik · Oct 11, 2010, 19:07:55

That's a slow hop to IDNet, then.

Niall · Oct 11, 2010, 19:35:41

Quote from: Lance on Oct 10, 2010, 23:06:55
Netn00b - if this is your second d/c this week, the first must have been BT working at your local exchange.

Niall, if it is important, you could tether your iPhone to the pc to share the data connection.

See now, this is the logic I need! That hadn't even occurred to me! Bleedin' ell

ou7shined · Oct 11, 2010, 19:45:43

Tracing route to ffm-bb2-link.telia.net [80.91.246.184]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms homeportal [192.168.1.254]
2 1 ms 47 ms 44 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 45 ms 44 ms 45 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 45 ms 44 ms 45 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
5 44 ms 44 ms 44 ms te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50.117]
6 45 ms 44 ms 45 ms te8-3.ccr01.lon01.atlas.cogentco.com [130.117.0.61]
7 44 ms * 45 ms te2-2.mpd01.lon01.atlas.cogentco.com [130.117.1.74]
8 183 ms 156 ms 157 ms ldn-b4-link.telia.net [213.248.70.237]
9 * 156 ms 218 ms ldn-bb2-link.telia.net [80.91.251.14]
10 164 ms 170 ms 186 ms prs-bb2-link.telia.net [80.91.247.240]
11 175 ms 378 ms 242 ms ffm-bb2-link.telia.net [80.91.246.184]

Trace complete.

Niall · Oct 11, 2010, 19:48:16

Telia are notoriously poo. I've had nightmare problems with them with two different ISPs and I know others on cable and other ISPs that have the same issue.

Kareha · Oct 11, 2010, 19:52:23

Emailed Support with my tracert, hopefully they can get it sorted

Nova · Oct 11, 2010, 19:59:32

Tracing route to 213-248-127-130.customer.teliacarrier.com [213.248.127.130]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.0.1
2 39 ms 36 ms 35 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 37 ms 35 ms 35 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 40 ms 33 ms 33 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148
.205]
5 34 ms 36 ms 35 ms te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
6 36 ms 38 ms 38 ms te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.
18]
7 36 ms 39 ms 37 ms vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2
.17]
8 150 ms 154 ms * ldn-b4-link.telia.net [213.248.70.237]
9 147 ms 145 ms 146 ms ldn-bb2-link.telia.net [80.91.254.21]
10 181 ms 155 ms 153 ms prs-bb1-link.telia.net [80.91.247.6]
11 165 ms 164 ms 162 ms ffm-bb2-link.telia.net [80.91.246.182]
12 209 ms 167 ms 164 ms ffm-b10-link.telia.net [80.91.247.185]

We had this before, it's routing from cogentco to telia, and Blizzard will tell us that it's IDnet that needs to whack the peers to get this sorted out.

sof2er · Oct 11, 2010, 20:19:23

Noticing the same thing on gameservers for steam games, connection to telia starts at 130+ ms.

4 20 ms 19 ms 20 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148
.205]
5 20 ms 20 ms 19 ms te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
6 20 ms 19 ms 20 ms te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.
18]
7 33 ms 20 ms 20 ms vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2
.17]
8 * 133 ms 132 ms ldn-b4-link.telia.net [213.248.70.237]
9 132 ms 132 ms * ldn-bb2-link.telia.net [80.91.251.14]

Presuming that ldn-bb2-link.telia.net stands for telia in london in which case it should be 20 ms and not 130

pctech · Oct 11, 2010, 20:27:52

Can you advise of the URL/IP you are using and I'll run a trace from here to see if the problem is beyond IDNet?

zappaDPJ · Oct 11, 2010, 20:31:26

Telia does have a rather poor reputation but since the outage latency into Telia has shot up. My current in-game latency is reading 870ms. I'll do a trace route when I've finished raiding. For the record no one in my group of 25 players is reporting anything higher than 130ms.

DorsetBoy · Oct 11, 2010, 20:39:23

Code Select

Tracing route to ffm-bb2-link.telia.net [80.91.246.184]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Vigor.router [192.168.1.1]
  2    29 ms    29 ms    29 ms  lns2.uan.thn.uk.murphx.net [89.145.254.70]
  3    29 ms    29 ms    29 ms  uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
  4    30 ms    31 ms    29 ms  ge2-6-1.cr1.core.thn.uk.murphx.net [89.145.254.161]
  5    29 ms    29 ms    30 ms  ge0-0-1.tr1.core.thn.uk.murphx.net [89.145.254.130]
  6    30 ms    31 ms    32 ms  xe-11-2-0-18.lon10.ip4.tinet.net [213.200.77.9]
  7    31 ms    29 ms    67 ms  xe-4-2-0.lon21.ip4.tinet.net [89.149.185.237]
  8    30 ms    29 ms    29 ms  213.200.78.238
  9    32 ms    31 ms    29 ms  ldn-bb2-link.telia.net [80.91.247.89]
 10    37 ms    38 ms    36 ms  prs-bb2-link.telia.net [80.91.247.240]
 11    65 ms    46 ms    61 ms  ffm-bb2-link.telia.net [80.91.246.184]

from an LLU line