League server #5 - NEW IP!

  • Hey - turns out IRC is out and something a little more modern has taken it's place... A little thing called Discord!

    Join our community @ https://discord.gg/JuaSzXBZrk for a pick-up game, or just to rekindle with fellow community members.

brajan

<b>League Adm</b><b>inistrator</b><br /><b>For</b>
Feb 25, 2004
5,416
113
/dev/null
League server #5 has changed.
It's no more hosted on UTA server.

New server #5 - hosted by pyrii.net
unreal://82.94.241.251:7777
 
In my tracert I have time outs all over the place and it refuses to finish a complete trace with spikes of around 250 LOL
 
Code:
1    <1 ms    <1 ms    <1 ms  10.0.32.1
2     1 ms     1 ms     1 ms  vl663.aggr2.sbo.ma.rcn.net [208.59.92.105]
3     1 ms     1 ms     1 ms  ge3-0.core3.sbo.ma.rcn.net [207.172.15.131]
4     7 ms     7 ms     8 ms  pos5-0.core3.nyw.ny.rcn.net [207.172.19.5]
5     6 ms     6 ms     6 ms  tge1-2.core4.nyw.ny.rcn.net [207.172.15.67]
6     6 ms     6 ms     7 ms  tge2-1.border1.nyw.ny.rcn.net [207.172.19.109]
7     7 ms    10 ms     6 ms  nyiix.he.net [198.32.160.61]
8    16 ms     7 ms    15 ms  10gigabitethernet1-1.core1.nyc4.he.net [72.52.92
5]
9    75 ms    75 ms    76 ms  10gigabitethernet1-2.core1.lon1.he.net [72.52.92
8]
0    83 ms    93 ms    83 ms  10gigabitethernet1-1.core1.ams1.he.net [72.52.92
2]
1    85 ms    86 ms    85 ms  ams-ix.sara.xs4all.net [195.69.144.48]
2    84 ms    85 ms    84 ms  0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5]
3   112 ms   211 ms   155 ms  0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]
4    87 ms    85 ms    85 ms  82.94.241.251

Seems like I have a bad hop but the whole "87/85/85" at the end is pretty sexy... Is this server located in the UK?
 
Well, right now Pinny's got a bit of a problem (TIMO CAUSED IT!!!!!!!!!!!!!!!!!!!!!!!!!!!! *points fingers*) and it seems it's messed up not letting players move... also it's causing me to have 27 ping :p:
 
Bah, don't blame Timo, blame me. It seems a recent kernel update might've been the cause of weird lagspikes. I set it back to the previous kernel so now it should be fine again.

This server is located in Amsterdam/The Netherlands. The datacenter it's in has amazing routing to most places in Europe so anyone with a decent internet connection in their country should get a nice ping on this server.

The second-to-last hop in the tracert above is because of QoS of that router that makes it pretty much ignore the tracert packets, hence the high ping. Doesn't make any difference with UT packets though. :)
 
Code:
tracert 82.94.241.251

Spårar route till 82.94.241.251 över ett maximalt antal av 30 hopp

  1     4 ms     4 ms     5 ms  gw3-no17.tbcn.telia.com [81.232.114.1]
  2    11 ms    11 ms    11 ms  kbn-bb1-pos1-0-0.telia.net [213.248.65.9]
  3    21 ms    21 ms    21 ms  s-bb1-link.telia.net [80.91.248.46]
  4    21 ms    21 ms    21 ms  s-b1-link.telia.net [80.91.254.117]
  5    23 ms    23 ms    22 ms  global-ic-120468-s-b1.c.telia.net [213.248.77.214]
  6    36 ms    37 ms    37 ms  XS4ALL.so-7-0-0.nar1.AMS1.gblx.net [146.82.33.178]
  7    34 ms    34 ms    34 ms  0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5]
  8    75 ms    79 ms    54 ms  0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]
  9    33 ms    32 ms    33 ms  82.94.241.251
 
Bah, don't blame Timo, blame me. It seems a recent kernel update might've been the cause of weird lagspikes. I set it back to the previous kernel so now it should be fine again.

This server is located in Amsterdam/The Netherlands. The datacenter it's in has amazing routing to most places in Europe so anyone with a decent internet connection in their country should get a nice ping on this server.

The second-to-last hop in the tracert above is because of QoS of that router that makes it pretty much ignore the tracert packets, hence the high ping. Doesn't make any difference with UT packets though. :)

In UT my F1 ping is really strange. ..... 130 120 110 95 86 60 30 130 120... etc.

When I trace my ping through a different line I'm getting much higher ping (although only 10 hops from USA), and that connection is much better. I can't guarantee which one I'll be routed through either so it's kind of crap at the moment. Server seems alright though and thanks a lot for providing it.
 
Code:
  1    <1 ms    <1 ms    <1 ms  10.0.32.1
  2     5 ms     5 ms     9 ms  wks1.eesco.com [71.248.180.1]
  3     5 ms     4 ms     4 ms  P3-1.LCR-01.BSTNMA.verizon-gni.net [130.81.37.96
]
  4    28 ms    29 ms    32 ms  130.81.17.199
  5    38 ms    29 ms    29 ms  10gigabitethernet1-3.core1.ash1.he.net [209.51.1
61.33]
  6   125 ms   124 ms   128 ms  10gigabitethernet1-2.core1.ams1.he.net [72.52.92
.98]
  7   113 ms   112 ms   133 ms  ams-ix.sara.xs4all.net [195.69.144.48]
  8   113 ms   112 ms   112 ms  0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5]
  9   111 ms   114 ms   111 ms  0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]
 10   118 ms   114 ms   114 ms  82.94.241.251

Less hops, higher ping :x
 
yesterday I had no connection to it at all now it seems ok but still a bouncy ping

25-35ms at dos , jumps up and down all time
 
Rute spores til 82.94.241.251 over et maksimum af 30 hop

1 2 ms 1 ms 1 ms . [192.168.2.1]
2 3 ms 2 ms 1 ms ftx-158-1.sydfynsnet.dk [85.27.158.1]
3 4 ms 121 ms 2 ms 85.27.128.74
4 8 ms 14 ms 5 ms sydfynsel-gw.ip.nianet.dk [83.136.88.121]
5 7 ms 4 ms 4 ms gi9-6.ccr01.cph01.atlas.cogentco.com [149.6.83.1
41]
6 12 ms 11 ms 10 ms te2-3.ccr01.ham01.atlas.cogentco.com [130.117.2.
149]
7 17 ms 15 ms 15 ms te1-2.ccr01.dus01.atlas.cogentco.com [130.117.3.
130]
8 21 ms 19 ms 19 ms te7-1.ccr01.ams03.atlas.cogentco.com [130.117.3.
89]
9 21 ms 19 ms 20 ms ams-ix.tc2.xs4all.net [195.69.144.166]
10 21 ms 19 ms 19 ms 0.so-2-0-0.xr4.1d12.xs4all.net [194.109.5.9]
11 21 ms 19 ms 20 ms 0.so-3-0-0.cr1.3d12.xs4all.net [194.109.5.58]
12 22 ms 20 ms 19 ms 82.94.241.251

Sporing fuldført.

C:\Users\Rasmus>
 
Please give Timo_Maas few days to set everything. In mean time report all problems so he'll be up-to-date about this subject.
 
>ping 82.94.241.251

Ping wird ausgeführt für 82.94.241.251 mit 32 Bytes Daten:

Antwort von 82.94.241.251: Bytes=32 Zeit=51ms TTL=116
Antwort von 82.94.241.251: Bytes=32 Zeit=48ms TTL=116
Antwort von 82.94.241.251: Bytes=32 Zeit=45ms TTL=117
Antwort von 82.94.241.251: Bytes=32 Zeit=44ms TTL=116

Ping-Statistik für 82.94.241.251:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 44ms, Maximum = 51ms, Mittelwert = 47ms

tracert 82.94.241.251

Routenverfolgung zu 82.94.241.251 über maximal 30 Abschnitte

1 <1 ms 1 ms <1 ms 192.168.0.1
2 9 ms 11 ms 9 ms lo1.br04.ber.de.hansenet.net [213.191.89.4]
3 8 ms 9 ms 9 ms 62.109.111.30
4 26 ms 27 ms 33 ms 213.191.66.25
5 * 26 ms 27 ms ae1-102.pr01.fra.de.hansenet.net [62.109.109.240]
6 27 ms 27 ms 27 ms decix-hansenet-3-de.fra.seabone.net [89.221.34.25]
7 44 ms 43 ms 43 ms gsr12416.ams.he.net [195.69.145.150]
8 43 ms 41 ms 41 ms ams-ix.sara.xs4all.net [195.69.144.48]
9 65 ms 45 ms 45 ms 0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5]
10 46 ms 47 ms 45 ms 0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]
11 46 ms 45 ms 45 ms 82.94.241.251

its ok...
 
Reply from 82.94.241.251: bytes=32 time=27ms TTL=116
Reply from 82.94.241.251: bytes=32 time=25ms TTL=116
Reply from 82.94.241.251: bytes=32 time=24ms TTL=116
Reply from 82.94.241.251: bytes=32 time=27ms TTL=116

1 <1 ms <1 ms <1 ms 192.168.0.1
2 16 ms 16 ms 7 ms 10.235.4.1
3 8 ms 22 ms 7 ms bagu-t2cam1-b-v117.inet.ntl.com [80.5.162.197]
4 9 ms 28 ms 8 ms bagu-t2core-b-ge-wan64.inet.ntl.com [195.182.17.37]
5 16 ms 10 ms 16 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.188.29]
6 32 ms 43 ms 17 ms pop-bb-a-so-300-0.inet.ntl.com [213.105.175.130
7 156 ms 163 ms 35 ms amst-ic-1-as0-0.inet.ntl.com [213.105.175.6]
8 25 ms 33 ms 24 ms ams-ix.sara.xs4all.net [195.69.144.48]
9 25 ms 47 ms 25 ms 0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5]
10 24 ms 25 ms 31 ms 0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]
11 63 ms 48 ms 25 ms unreal.pyrii.net [82.94.241.251]
 
Tbh, the only way to truly test a server is to play on it.

Since ping and tracert use ICMP packets and UT uses UDP packets. UDP packets are usually not throttled as much as ICMP ones are. A tracert may look bad with high numbers, but that might not even affect anything at all.

As long as your normal ping is stable it should be fine though. Since a high ping isn't really a problem, a fluctuating ping is much worse. (try the command: "ping -t 82.94.241.251" and see if it has any big spikes while running it for a minute)

Anyway, please try it to see how it goes in a real match. This server runs on a Windows NT4 VMware box so it might be quite a different experience (better or worse, who knows) from the current league servers.
 
Code:
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
R[B]eply from 82.94.241.251: bytes=32 time=94ms TTL=110[/B]
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=84ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=86ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
[B]Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=114ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112[/B]
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=114ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=111ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=111ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=114ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=117ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=114ms TTL=111
Reply from 82.94.241.251: bytes=32 time=115ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=111ms TTL=111
Reply from 82.94.241.251: bytes=32 time=135ms TTL=111
Reply from 82.94.241.251: bytes=32 time=130ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=115ms TTL=112
Reply from 82.94.241.251: bytes=32 time=111ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=114ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=114ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=111ms TTL=111
Reply from 82.94.241.251: bytes=32 time=115ms TTL=111
Reply from 82.94.241.251: bytes=32 time=114ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=114ms TTL=111
Reply from 82.94.241.251: bytes=32 time=114ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=111ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=111ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=111ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=114ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=111ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=111ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=111ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=111ms TTL=112
Reply from 82.94.241.251: bytes=32 time=116ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=114ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=112
Reply from 82.94.241.251: bytes=32 time=111ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=111ms TTL=112
Reply from 82.94.241.251: bytes=32 time=114ms TTL=111
Reply from 82.94.241.251: bytes=32 time=111ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=111ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=111ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=115ms TTL=111
Reply from 82.94.241.251: bytes=32 time=114ms TTL=112
Reply from 82.94.241.251: bytes=32 time=114ms TTL=111
Reply from 82.94.241.251: bytes=32 time=115ms TTL=112
Reply from 82.94.241.251: bytes=32 time=111ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=115ms TTL=112
Reply from 82.94.241.251: bytes=32 time=111ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=111
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=112ms TTL=112
Reply from 82.94.241.251: bytes=32 time=113ms TTL=111
Reply from 82.94.241.251: bytes=32 time=114ms TTL=111
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
[B]Reply from 82.94.241.251: bytes=32 time=85ms TTL=110
Request timed out.
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110[/B]
Reply from 82.94.241.251: bytes=32 time=85ms TTL=110

It starts steady at 85, spikes to 94 once and then starts leveling around 113... then back to 85?[I[/I]
 
Last edited:
Looks like it switches the routing after a while.
You know there're multiple fibres running through the ocean, it usually tries to find the shortest route, but if that one doesn't work then it tries to find another one. The fibres aren't really close to eachother so that might explain 30ms difference. Also the difference in hops. I think it has something to do with the TTL as well, but I'm not an expert so...

Anyway, this is something that's happening on your side of the ocean so you should ask your ISP to deal with it. :P