Ultima online/sprintlink connection probs

[ASMO]

i play Ultima Online with normally a ping of 30-40 which is great but as of tonight i pinging it at 300+ i did a tracert and i see the problem with the sprintlink servers but the othe people i play UO with [all on ntl] are fine im on the mapperley server any ideas?
tracert btw

Tracing route to 159.153.156.138 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.0.1
2 10 ms 11 ms 8 ms 10.145.207.254
3 11 ms 9 ms 10 ms nott-t2cam1-b-v137.inet.ntl.com [80.4.46.193]
4 12 ms 9 ms 10 ms nott-t2core-b-ge-wan73.inet.ntl.com [80.1.79.20
]
5 14 ms 9 ms 12 ms nth-bb-b-so-300-0.inet.ntl.com [62.253.188.37]
6 11 ms 14 ms 32 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
7 13 ms 15 ms 34 ms bir-bb-b-so-200-0.inet.ntl.com [62.253.185.106]
8 13 ms 15 ms 34 ms bir-bb-a-ae0-0.inet.ntl.com [62.253.185.153]
9 12 ms 14 ms 41 ms man-bb-b-so-700-0.inet.ntl.com [62.253.185.134]
10 227 ms 222 ms 234 ms sl-gw11-lon-8-0.sprintlink.net [213.206.159.245
11 225 ms 223 ms 223 ms sl-bb21-lon-11-0.sprintlink.net [213.206.128.58
12 227 ms 225 ms 226 ms sl-gw21-lon-1-1.sprintlink.net [213.206.128.102
13 231 ms 243 ms 232 ms sle-elect6-7-0.sprintlink.net [213.206.159.166]
14 243 ms 233 ms 232 ms 159.153.156.3
15 239 ms 239 ms 246 ms 159.153.156.138
Trace complete.
ping

C:\Documents and Settings\Anthony>ping 159.153.156.138
Pinging 159.153.156.138 with 32 bytes of data:
Reply from 159.153.156.138: bytes=32 time=227ms TTL=50
Reply from 159.153.156.138: bytes=32 time=233ms TTL=50
Reply from 159.153.156.138: bytes=32 time=229ms TTL=50
Reply from 159.153.156.138: bytes=32 time=226ms TTL=50
Ping statistics for 159.153.156.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 226ms, Maximum = 233ms, Average = 228ms:Yikes:
ASMO

[Nikko]

I am also on Mapperley UBR, just got this for a comparison:


Tracing route to 159.153.156.138 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.xxx.xxx
2 9 ms 10 ms 9 ms 10.145.xxx.xxx
3 9 ms 10 ms 8 ms nott-t2cam1-b-v137.inet.ntl.com [80.4.46.193]
4 11 ms 9 ms 9 ms nott-t2core-b-ge-wan74.inet.ntl.com [80.1.79.201
]
5 13 ms 10 ms 19 ms nth-bb-b-so-200-0.inet.ntl.com [62.253.185.37]
6 17 ms 13 ms 13 ms lee-bb-a-so-600-0.inet.ntl.com [62.253.185.102]

7 13 ms 13 ms 13 ms lee-bb-b-ae0-0.inet.ntl.com [62.253.187.186]
8 16 ms 13 ms 14 ms man-bb-a-so-700-0.inet.ntl.com [62.253.185.193]

9 14 ms 13 ms 13 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
10 29 ms 29 ms 30 ms sl-gw11-lon-8-0.sprintlink.net [213.206.159.245]

11 33 ms 32 ms 31 ms sl-bb20-lon-11-0.sprintlink.net [213.206.128.56]

12 28 ms 27 ms 26 ms sl-gw21-lon-1-1.sprintlink.net [213.206.128.102]

13 41 ms 33 ms 31 ms sle-elect6-7-0.sprintlink.net [213.206.159.166]

14 36 ms 34 ms 34 ms 159.153.156.3
15 31 ms 31 ms 32 ms 159.153.156.138

Trace complete.

Pinging 159.153.156.138 with 32 bytes of data:

Reply from 159.153.156.138: bytes=32 time=29ms TTL=50
Reply from 159.153.156.138: bytes=32 time=27ms TTL=50
Reply from 159.153.156.138: bytes=32 time=28ms TTL=50
Reply from 159.153.156.138: bytes=32 time=27ms TTL=50

Ping statistics for 159.153.156.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 29ms, Average = 27ms

[Ignition]

Looks like a problem with Sprintlink's routing to your IP range, quite odd that, you'd expect them to have a really big subnet to route to, I'd guess Nikko has a completely different IP address from you.

Is this still an issue? Dynamic nature of routing means these things can and do fix themselves, if not someone at Sprint may have had a play and fixed it.

For comparison, my trace to that server is below, uses almost completely different route to you gentlemen

Tracing route to 159.153.156.138 over a maximum of 30 hops

1 2 ms <1 ms <1 ms gatelock-corporate.inside.net [192.168.253.1]
2 2 ms 1 ms 1 ms x-modem.inside.net [10.0.0.2]
3 21 ms 88 ms 96 ms 82-197-73-6.hi-velocity.net [82.197.73.6]
4 23 ms 21 ms 19 ms 82-197-65-226.hi-velocity.net [82.197.65.226]
5 22 ms 21 ms 21 ms 82.197.95.90
6 22 ms 19 ms 19 ms 82.197.95.45
7 23 ms 21 ms 21 ms 82.197.95.180
8 22 ms 21 ms 20 ms ge-6-0.core2.London1.Level3.net [212.187.131.46]
9 19 ms 19 ms 19 ms sl-bb21-lon-6-0.sprintlink.net [213.206.131.21]
10 21 ms 21 ms 21 ms sl-gw21-lon-1-1.sprintlink.net [213.206.128.102]
11 23 ms 23 ms 23 ms sle-elect6-7-0.sprintlink.net [213.206.159.166]
12 23 ms 23 ms 25 ms 159.153.156.3
13 23 ms 23 ms 21 ms 159.153.156.138

Pinging 159.153.156.138
with 32 bytes data (60 bytes IP):

Reply from 159.153.156.138: seq=0000 time=22.392ms TTL=53 ID=5225
Reply from 159.153.156.138: seq=0001 time=20.569ms TTL=53 ID=5226
Reply from 159.153.156.138: seq=0002 time=21.023ms TTL=53 ID=5227
Reply from 159.153.156.138: seq=0003 time=23.257ms TTL=53 ID=5228

Statistics for 159.153.156.138:
Packets: sent=4, rcvd=4, error=0, lost=0 (0% loss) in 1.523276 sec
RTTs of replies in ms: min/avg/max: 20.569 / 21.810 / 23.257

[ASMO]

lasted about 3 hrs last night... was fine this morning
ASMO