Author Topic: what's up with the server? (Read 530 times)

Pooface · « **on:** July 09, 2006, 02:39:01 PM »

if i can manage to log on at all, i lose udp straight away and none of the buttons on the clipboard work...

a tad annoying, anything that there can be done to get it working faster?

B@tfinkV · « **Reply #1 on:** July 09, 2006, 02:50:00 PM »

i had to reboot my PC just t get back online, then lost udp in 5 mins.

Pooface · « **Reply #2 on:** July 09, 2006, 02:53:39 PM »

Quote

Originally posted by B@tfinkV
i had to reboot my PC just t get back online, then lost udp in 5 mins.

same here, reboot, try again, no effect, still a downright awful connection, despite telling me i had a ping of 120

Skuzzy · « **Reply #3 on:** July 09, 2006, 03:20:49 PM »

Just checked the server and it is fine. I logged right in (from home) and response felt pretty crisp.

Probably the overseas Internet connection. That's a guess. Run a PingPlot for a couple of minutes to check.

In the past, BT has not been the most consistent ISP around. Nildram usually does better, overall.

paulobrien6969 · « **Reply #4 on:** July 09, 2006, 03:27:09 PM »

no problems here on UK NTL

MadBull · « **Reply #5 on:** July 09, 2006, 04:17:35 PM »

I live in Illinois and I keep having a problem with my 7th hop.

Ip 144.232.8.219 DSNS Name sl-st20-chi-12-0.sprintlin

it will run ok for a while then starts jumping around with packet loss from 10 up to 70 percent.

I haven't had any connection issues in a long time. Well until yesterday anyway.

And on both days I believe this hop to be the problem. So if your hopping thru this server it is probably at least part of your problem.

Schatzi · « **Reply #6 on:** July 09, 2006, 06:16:15 PM »

Was online all evening (MA/TA) without loosing UDP (Germany here). Things seemed a bit warpy though....

Edit: Ran some ping plots...

MA server:

Target Name: N/A
IP: 206.16.60.39
Date/Time: 10.07.2006 01:17:47

1 0 ms 1 ms 1 ms 1 ms 1 ms 0 ms 1 ms 1 ms 0 ms 0 ms localhost [192.168.1.1]
2 -32764 ms 19 ms 19 ms 20 ms 20 ms 21 ms 20 ms 19 ms 20 ms 20 ms dslc-082-082-064-001.pools.arcor-ip.net [82.82.64.1]
3 53 ms 20 ms 20 ms 21 ms 20 ms 19 ms 20 ms 20 ms 21 ms 20 ms han-145-254-11-237.arcor-ip.net [145.254.11.237]
4 22 ms 23 ms 23 ms 24 ms 22 ms 22 ms 23 ms 22 ms 21 ms 22 ms hmb-145-254-18-146.arcor-ip.net [145.254.18.146]
5 23 ms 24 ms 24 ms 23 ms 24 ms 23 ms 22 ms 23 ms 22 ms 24 ms so-2-0-0.ar2.ham1.gblx.net [64.215.181.93]
6 105 ms 104 ms 106 ms 105 ms 104 ms 105 ms 105 ms 106 ms 105 ms 126 ms so7-0-0-2488M.ar3.NYC1.gblx.net [67.17.79.10]
7 11 ms 10 ms 9 ms 11 ms 10 ms * 10 ms 12 ms 11 ms 103 ms ggr2-p351.n54ny.ip.att.net [192.205.33.53]
8 * * * * * * * * * * [-]
9 * * * * * * * * * * [-]
10 * * * * * * * * * * []
11 54 ms 50 ms 48 ms 50 ms 49 ms 48 ms 50 ms 48 ms 52 ms 49 ms tbr2-p033901.n54ny.ip.att.net [12.123.0.94]
12 * 345 ms 344 ms 344 ms 346 ms 1 ms -32764 ms -32764 ms -32764 ms 189 ms [12.122.255.82]
13 18 ms 19 ms 19 ms 17 ms 19 ms 18 ms 19 ms 18 ms 18 ms 20 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54]
14 * * * * * * * * * * [-]
15 7 ms 9 ms 8 ms 7 ms 9 ms 8 ms 7 ms 8 ms 7 ms 9 ms tbr1-cl27.wswdc.ip.att.net [12.122.9.149]
16 4 ms 3 ms 4 ms 3 ms 2 ms 4 ms 3 ms 4 ms 3 ms 2 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
17 3 ms 2 ms 2 ms 5 ms 2 ms 5 ms 3 ms 2 ms 3 ms 2 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
18 2 ms 3 ms 2 ms 5 ms 4 ms 3 ms 4 ms 2 ms 5 ms 2 ms br2-a3120s9.dlstx.ip.att.net [12.123.16.213]
19 18 ms 20 ms 19 ms * 21 ms 4 ms 547 ms 19 ms 54 ms 20 ms mdf1-bi8k-1-eth-1-1.dal1.attens.net [63.241.192.250]
20 142 ms 141 ms 143 ms 142 ms 143 ms 142 ms 143 ms 142 ms 142 ms 143 ms [206.16.60.39]

Other Arenas:

Target Name: N/A
IP: 206.16.60.38
Date/Time: 10.07.2006 01:19:16

1 1 ms 0 ms 1 ms 1 ms 1 ms 0 ms 0 ms 0 ms 0 ms 0 ms localhost [192.168.1.1]
2 21 ms 19 ms 21 ms 20 ms 20 ms 19 ms 22 ms -32764 ms 19 ms 21 ms dslc-082-082-064-001.pools.arcor-ip.net [82.82.64.1]
3 21 ms 20 ms 22 ms 20 ms 22 ms 20 ms 19 ms 52 ms 19 ms 21 ms han-145-254-11-233.arcor-ip.net [145.254.11.233]
4 21 ms 22 ms 21 ms 23 ms 22 ms 24 ms 21 ms 23 ms 22 ms 21 ms hmb-145-254-18-142.arcor-ip.net [145.254.18.142]
5 22 ms 23 ms 23 ms 24 ms 27 ms 22 ms 23 ms 22 ms 24 ms 23 ms so-2-0-0.ar2.ham1.gblx.net [64.215.181.93]
6 105 ms 106 ms 105 ms 104 ms 105 ms 114 ms 106 ms 104 ms 106 ms 105 ms so7-0-0-2488M.ar3.NYC1.gblx.net [67.17.79.10]
7 3 ms 1 ms -32764 ms -32764 ms -32764 ms * 343 ms * 344 ms 343 ms [12.122.255.82]
8 * * * * * * * * * * [12.122.255.82]
9 * * * * * * * * * * [-]
10 10 ms 9 ms 11 ms 10 ms 11 ms 10 ms 11 ms 11 ms 9 ms 11 ms ggr2-p351.n54ny.ip.att.net [192.205.33.53]
11 50 ms 49 ms 50 ms 49 ms 48 ms 49 ms 48 ms 49 ms 48 ms 50 ms tbr2-p033901.n54ny.ip.att.net [12.123.0.94]
12 * * * * * * * * * * [-]
13 17 ms 19 ms 18 ms 21 ms 18 ms 20 ms 20 ms 19 ms 18 ms 17 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54]
14 * * * * * * * * * * [-]
15 5 ms 8 ms 7 ms 8 ms 7 ms 5 ms 6 ms 6 ms 7 ms 6 ms tbr1-cl17.attga.ip.att.net [12.122.10.70]
16 3 ms 16 ms 2 ms 2 ms 4 ms 4 ms 4 ms 3 ms 4 ms 3 ms tbr2-cl1835.attga.ip.att.net [12.122.9.158]
17 5 ms 20 ms 5 ms 4 ms 6 ms 21 ms 6 ms 5 ms 4 ms 6 ms tbr1-cl13.dlstx.ip.att.net [12.122.2.89]
18 3 ms 17 ms 4 ms 2 ms 2 ms 19 ms 2 ms 4 ms 3 ms 2 ms br2-a340s8.dlstx.ip.att.net [12.123.16.209]
19 3 ms 4 ms 19 ms 19 ms 19 ms 2 ms 19 ms 17 ms 19 ms 18 ms [63.241.192.42]
20 142 ms 144 ms 142 ms 144 ms 142 ms 148 ms 143 ms 141 ms 143 ms 142 ms [206.16.60.38]

airbull · « **Reply #7 on:** July 10, 2006, 02:18:06 AM »

Also had problems on Sunday all day.
Just checked again & cant see a ping to any server. Piing plot shows bad connection where it goes across the water I think. What can be done about it. Is it ring Bt or what ???
Target Name: (resolving host name)
IP: 206.16.60.39
Date/Time: 10/07/2006 08:12:37

1 3 ms 0 ms http://www.routerlogin.com [192.168.0.1]
2 10 ms 9 ms [217.41.191.250]
3 9 ms 9 ms [217.41.191.161]
4 10 ms 9 ms [217.41.175.9]
5 9 ms 9 ms [217.41.175.66]
6 10 ms 9 ms [217.41.175.78]
7 9 ms 9 ms [217.41.219.46]
8 8 ms 9 ms [217.47.154.99]
9 9 ms 8 ms core1-pos9-2.bletchley.ukcore.bt.net [194.72.31.153]
10 11 ms 10 ms core1-pos1-4.ealing.ukcore.bt.net [195.99.120.209]
11 10 ms 10 ms transit1-pos5-0.ealing.ukcore.bt.net [194.72.17.122]
12 10 ms 10 ms t2c1-p3-0.uk-eal.eu.bt.net [166.49.168.5]
13 138 ms 86 ms t2c1-p4-0.us-ash.eu.bt.net [166.49.164.110]
14 86 ms 86 ms [12.118.44.37]
15 N/A N/A [] 100% packet loss from the next 3 hops that are not showing
16 N/A N/A []
17 N/A N/A []
18 138 ms 118 ms br2-a3120s9.dlstx.ip.att.net [12.123.16.213]
19 N/A N/A []
20 118 ms 118 ms mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.222]

Skuzzy · « **Reply #8 on:** July 10, 2006, 09:20:15 AM »

It's not unusual for BT to have issues like this. I would suggest all you BT users get these traces to them. Seems to happen this time of year without fail.

If Sprint is in your path, you can expect some degree of problems. They will be erratic. They always have been.

airbull · « **Reply #9 on:** July 10, 2006, 11:28:40 AM »

Thanks seems to have cleared up for now.

Skuzzy · « **Reply #10 on:** July 10, 2006, 02:00:11 PM »

Actually, part (if not most) of the problem was the World Cup.

straffo · « **Reply #11 on:** July 10, 2006, 03:05:50 PM »

Skuzzy can you check 63.241.192.46 ?

My ping on this host varied from 140 to 425 ???

Skuzzy · « **Reply #12 on:** July 10, 2006, 03:11:48 PM »

straffo, I have tried from several different sources and cannot get to that IP address.

straffo · « **Reply #13 on:** July 10, 2006, 03:52:21 PM »

strange because for me it's the last hop before MA :

Target Name: N/A
IP: 206.16.60.39
Date/Time: 10/07/2006 22:50:54

1 0 ms 0 ms 0 ms 1 ms [192.168.0.1]
2 21 ms 21 ms 22 ms 21 ms [84.7.168.1]
3 21 ms 22 ms 76 ms 88 ms [80.124.249.165]
4 21 ms 22 ms 25 ms 23 ms [195.115.104.158]
5 22 ms 23 ms 23 ms 57 ms [195.115.106.86]
6 113 ms 26 ms * * 69.236.96-84.rev.gaoland.net [84.96.236.69]
7 24 ms 24 ms 23 ms 25 ms V4073.cbv3-co-1.n9uf.net [62.39.148.85]
8 24 ms 23 ms 23 ms 23 ms V4093.bou1-co-1.n9uf.net [62.39.148.6]
9 23 ms 23 ms 26 ms 24 ms V4081.par1-co-1.n9uf.net [62.39.148.54]
10 24 ms 24 ms 24 ms 24 ms [212.73.253.5]
11 22 ms 24 ms 24 ms 34 ms ge-7-0-0.mp2.Paris1.Level3.net [4.68.115.217]
12 97 ms -32764 ms -32764 ms 97 ms as-2-0.bbr2.NewYork1.Level3.net [4.68.128.138]
13 -32764 ms 194 ms -32764 ms 140 ms ae-23-52.car3.NewYork1.Level3.net [4.68.97.50]
14 98 ms 97 ms 101 ms 100 ms ggr2-p360.n54ny.ip.att.net [192.205.33.93]
15 139 ms 139 ms 140 ms 138 ms tbr2-p033901.n54ny.ip.att.net [12.123.0.94]
16 139 ms 141 ms 140 ms 140 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54]
17 143 ms 143 ms 142 ms 143 ms tbr1-cl27.wswdc.ip.att.net [12.122.9.149]
18 141 ms 144 ms 143 ms 144 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
19 141 ms 144 ms 142 ms 143 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
20 141 ms 140 ms 141 ms 141 ms br2-a3120s9.dlstx.ip.att.net [12.123.16.213]
21 141 ms 141 ms 142 ms 143 ms [12.122.255.78]
22 589 ms 142 ms 141 ms 141 ms [63.241.192.46]
23 141 ms 144 ms 143 ms 142 ms [206.16.60.39]

Skuzzy · « **Reply #14 on:** July 10, 2006, 04:15:25 PM »

Oh. That explains it. From our location, we cannot get to that router. It is physically removed from us due to proximity.

In other words, it is a hard coded route which is fully asynchronous.