Is Europe broken?

[ChillyDawg]

From all the evidence i can see, from my point of view, i rekon Europe is broken. Does anyone else Using Demon(ISP) and possibly ISDN as well, but not ness. have any bad connection problems.
By this i mean, can you connect every time, and if not, how many attempts?


Dawg

 

[elanza]

HMMN this may just be coincidence but i posted my patching problems earlier this week I just can not patch in to game, but i also use isdn and demon, maybe it is not just me then.

 

[Nalikin]

i was using bt and ISDN uptil today , didn't have a problem connecting .

 

[lyne]

I've got the same problem, I have Demon ISDN and so does a guy who lives near me.. We both have problems getting into DAoC, and when playing it's packet loss and lag a fair old bit.

From looking at a traceroute there is increased latency over the Open Transit network, about steps 9-10 theoretically London to France:

Tracing the route to 193.252.123.13

1 demon-du.demon.co.uk (158.152.1.222) 28 msec 28 msec 28 msec
2 anchor-ndu-as20-l0.access.demon.net (194.159.171.60) 28 msec 32 msec 32 msec
3 anchor-core-1-fxp3.router.demon.net (195.173.57.251) 32 msec 28 msec 28 msec
4 anchor-border-1-e12.router.demon.net (194.159.7.202) 88 msec * 32 msec
5 tele-border-1-e36.router.demon.net (194.159.36.234) 32 msec 32 msec 28 msec
6 215.ge4-0.mpr1.lhr1.uk.mfnx.net (208.185.188.113) 28 msec 32 msec 28 msec
7 pos5-0.mpr2.lhr1.uk.mfnx.net (208.185.156.14) 32 msec 32 msec 28 msec
8 P8-3.LONBB1.London.opentransit.net (193.251.154.65) 28 msec 32 msec 28 msec
9 P13-0.PASCR1.Pastourelle.opentransit.net (193.251.154.225) 160 msec 124 msec 124 msec
10 P4-0.BAGCR3.Bagnolet.opentransit.net (193.251.241.118) 124 msec 124 msec 120 msec
11 P1-0.BAGBB1.Bagnolet.opentransit.net (193.251.241.145) 544 msec 120 msec 124 msec
12 WanadooPortails1.GW.opentransit.net (193.251.251.58) 164 msec 164 msec 120 msec
13 * * *
14 * * *

Which I don't get if I dial using Freeserve:

Tracing route to 193.252.123.13 over a maximum of 30 hops

1 35 ms 35 ms 35 ms cougar.lns.watford.access.planet.net.uk [195.92.66.189]
2 32 ms 35 ms 37 ms lettuce.as5388.net [195.92.66.2]
3 36 ms 37 ms 35 ms 195.50.116.189
4 36 ms 38 ms 35 ms unknown.Level3.net [212.187.131.150]
5 48 ms 47 ms 50 ms P7-0.LONBB1.London.opentransit.net [193.251.240.217]
6 51 ms 47 ms 44 ms P13-0.PASCR1.Pastourelle.opentransit.net [193.251.154.225]
7 47 ms 47 ms 44 ms P4-0.BAGCR3.Bagnolet.opentransit.net [193.251.241.118]
8 49 ms 50 ms 50 ms P1-0.BAGBB1.Bagnolet.opentransit.net [193.251.241.145]
9 49 ms 50 ms 50 ms WanadooPortails1.GW.opentransit.net [193.251.251.58]
10 48 ms 50 ms 50 ms 193.252.122.10
11 71 ms 55 ms 53 ms 193.252.123.13

It looks like the latency may be a factor, also the trace stops at step 12 on the first, but continues through on the second.

Lyne.

 

[ChillyDawg]

That looks pretty similar to my Tracert i did, i am a bit miffed at Demon tbh, supposedly the best ISP around. Well. Il complain a bit to them a bit, i suggest u do too maybe theyl change their routing.

Dawg

 

[lyne]

Yeah I'll fire off a mail to 'em.. I think most of the big ISP's have private peering with Open Transit anyway, I'm surprised they don't.

Lyne.

 

[ChillyDawg]

Cool,
Anyone else that feels like it should send an email, regardless of whether your a custmer of Demon

Dawg

 

[Elvewen]

I am STILL having this problem.. I have since last Friday (Dial Up BTW).

There web site says it's fixed but when (and if) I can log on to DAoC I am getting contant yellow on the perf meter.

So I am forced to play low lvl chars as my biguns will get well slaughterd


I HATE THEM !!!!!!!!!!!!!!!!!!!


But they are the only one's I have found (except bloody AOL) that wont kick me after 2 hours ( and AOL wont let you share the account between two machines at once ).

 

[GrimReaper]

Same problem here with Demon ISDN. Had the problem for a week. Lots of packet loss and poor performance. Seems to have improved a little since massive problems last week, but still a lot of ld's and lag.

Worrying that they report no problems on the Demon site. Reckon we should all email them.

 

[lyne]

Well to be honest it doesn't look like a Demon problem, the problem seems to be with Open Transit.. Their link between London and Paris is running at 130ms (ish).. If this was trans-atlantic I'd expect about 80ms but for a quick hop over the channel it's too much. Also there is that mad path problem which worries me. Without being able to see a reverse trace I can't confirm how the traffic is coming back.

The best thing to do would be to mail GOA and create a support ticket, I'll do that this evening... Asking Demon to shift their peering over to another IX may work, but they are unlikely to do so, also we run the risk of having higher latency.

I'll mail GOA tonight about this and see if we can get it fixed. It's a royal pain, as I keep getting cut off every 2 hours when I'm on freeserve.

 

[ChillyDawg]

good plan, as far as i can tell, the severity of the problem has decreased for me, a LITTLE, but it is still there. I can usually connect but reconnecting is a different storey, if i go LD i can very rarely reconnectl promptly, it usally taking a good 30 mins for the connection to be up again

Dawg

 

[lyne]

Good news, Open Transit have a looking glass that I was able to query..

Basically they are sending traffic for Demon back via the USA:

Tracing the route to <SNIP> My host.
1 P3-0.PASCR3.Pastourelle.opentransit.net (193.251.241.126) 0 msec
P4-0.BAGCR3.Bagnolet.opentransit.net (193.251.241.118) 0 msec
P3-0.PASCR3.Pastourelle.opentransit.net (193.251.241.126) 0 msec
2 So3-0-0.TELBB1.Telehouse.opentransit.net (193.251.241.173) 0 msec 0 msec
So0-0-0.TELBB1.Telehouse.opentransit.net (193.251.241.177) 0 msec
3 Cw-Euro.GW.opentransit.net (193.251.252.142) 0 msec 0 msec 0 msec
4 bcr1-so-2-0-0.Paris.cw.net (208.172.251.165) [AS 3561] 0 msec 0 msec 0 msec
5 dcr1-loopback.NewYork.cw.net (206.24.194.99) [AS 3561] 80 msec
dcr2-loopback.NewYork.cw.net (206.24.194.100) [AS 3561] 80 msec 80 msec
6 agr1-so-6-0-0.NewYork.cw.net (206.24.207.194) [AS 3561] 80 msec
agr2-so-2-0-0.NewYork.cw.net (206.24.207.182) [AS 3561] 80 msec
agr1-so-0-0-0.NewYork.cw.net (206.24.207.50) [AS 3561] 80 msec
7 iar4-loopback.NewYork.cw.net (206.24.194.39) [AS 3561] 80 msec 80 msec 80 msec
8 demon-internet.NewYork.cw.net (208.173.135.162) [AS 3561] 76 msec 80 msec 80 msec
9 lon1-core-11-2-0-1-1-101.router.demon.net (194.159.176.97) [AS 2529] 92 msec 88 msec 88 msec
10 lon1-border-1-224.router.demon.net (195.173.72.13) [AS 2529] 88 msec 88 msec 88 msec
11 tele-border-4-233.router.demon.net (195.173.72.54) [AS 2529] 88 msec 88 msec 88 msec
12 tele-service-21-229.router.demon.net (195.173.72.34) [AS 2529] 88 msec 100 msec 88 msec
13 tele-service-11-136.router.demon.net (194.159.176.66) [AS 2529] 92 msec 88 msec 88 msec
14 tele-access-1-165.router.demon.net (194.159.36.145) [AS 2529] 88 msec 88 msec 88 msec.
.
.

I'll add this to my ticket I have open with GOA.

Lyne

 

[ChillyDawg]

Lol, to US? stupid europeans!
That should be temporary reroute caused by something broken i rekon, either that or they jus messed up...


Dawg

 

[lyne]

Sometimes I just wanna cry...

The lag is due to OpenTransit, the packet loss due to Demon.

=-=-=-=
traceroute 194.159.7.202 <- a router on the way out of the Demon network.

Success rate is 94 percent (947/1000), round-trip min/avg/max = 28/45/476 ms
=-=-=-=
<DEMON>
Nov 04, 10:36 allison We are experiencing packet loss with customers routing via Anchorage House. Engineers are investigating this with our suppliers.
</DEMON>

/cry

Lyne.

PS: I'm going to shurrup now until it's both fixed Sorry to warble on so much!