[R45]

Anyone experiencing very high latency? Mine has never been this bad, started happening this weekend. I'm getting about 900-1300ms ping to most places on the net (sometimes worse).

Quote

traceroute: Warning: www.yahoo.com has multiple addresses; using 68.142.197.79
traceroute to p16.www.mud.yahoo.com (68.142.197.79), 30 hops max, 40 byte packets
1  internet.home (10.0.0.1)  0.243 ms  0.188 ms  0.167 ms
2  tservq.tstt.net.tt (209.94.205.25)  9.099 ms  9.821 ms  10.086 ms
3  routf.tstt.net.tt (209.94.205.7)  12.055 ms route.tstt.net.tt (209.94.205.6)  12.291 ms  13.041 ms
4  sl-gw8-orl-4-0-TS7.sprintlink.net (160.81.138.253)  1299.663 ms bar1-serial4-1-0.Miami.savvis.net (208.172.100.201)  92.542 ms sl-gw8-orl-4-0-TS7.sprintlink.net (160.81.138.253)  1366.816 ms
5  sl-bb20-orl-0-0.sprintlink.net (144.232.2.232)  919.057 ms acr1-loopback.Miami.savvis.net (208.172.98.61)  854.815 ms  1099.526 ms
6  sl-bb20-fw-9-3.sprintlink.net (144.232.19.141)  1122.511 ms bcs1-so-3-1-0.Dallas.savvis.net (204.70.193.186)  962.703 ms sl-bb20-fw-9-3.sprintlink.net (144.232.19.141)  1199.685 ms
7  bcr2-so-0-0-0-500.Dallas.savvis.net (204.70.193.13)  1003.360 ms sl-st21-dal-1-0.sprintlink.net (144.232.20.17)  1041.608 ms  1115.033 ms
8  sl-yahoo3-23-0.sprintlink.net (144.228.250.78)  1055.705 ms  1037.465 ms ohr1-pos-1-0.FortWorthda1.savvis.net (208.172.129.230)  1038.021 ms
9  UNKNOWN-68-142-193-19.yahoo.com (68.142.193.19)  1205.971 ms csr1-ve242.FortWorthda1.savvis.net (216.39.64.58)  1233.978 ms UNKNOWN-68-142-193-17.yahoo.com (68.142.193.17)  1246.888 ms
10  216.39.86.142 (216.39.86.142)  1258.269 ms p16.www.mud.yahoo.com (68.142.197.79)  1148.655 ms  1153.365 ms

This was at 5:53PM in West Moorings. Latency was a bit lower earlier in the day but still around 600-700ms for anywhere on the net. From the traceroute, you can see my network is fine and also my route to TSTT is fine.

Another traceroute

Quote

traceroute: Warning: www.yahoo.com has multiple addresses; using 68.142.197.73
traceroute to p10.www.mud.yahoo.com (68.142.197.73), 30 hops max, 40 byte packets
1  internet.home (10.0.0.1)  0.225 ms  0.179 ms  0.168 ms
2  tservq.tstt.net.tt (209.94.205.25)  9.516 ms  11.319 ms  8.094 ms
3  routf.tstt.net.tt (209.94.205.7)  10.078 ms route.tstt.net.tt (209.94.205.6)  9.790 ms routf.tstt.net.tt (209.94.205.7)  9.830 ms
4  bar1-serial4-1-0.Miami.savvis.net (208.172.100.201)  91.137 ms sl-gw8-orl-3-0-TS5.sprintlink.net (160.81.34.245)  1223.764 ms bar1-serial4-1-0.Miami.savvis.net (208.172.100.201)  90.446 ms
5  sl-bb20-orl-0-0.sprintlink.net (144.232.2.232)  1142.401 ms  1140.284 ms  1164.370 ms
6  bcs1-so-3-1-0.Dallas.savvis.net (204.70.193.186)  1159.531 ms sl-bb20-fw-9-3.sprintlink.net (144.232.19.141)  1157.957 ms bcs1-so-3-1-0.Dallas.savvis.net (204.70.193.186)  1178.376 ms
7  sl-st21-dal-13-0.sprintlink.net (144.232.20.81)  1124.802 ms  1102.394 ms bcr1-so-0-0-0-500.Dallas.savvis.net (204.70.193.9)  1176.234 ms
8  ohr1-pos-4-0.FortWorthda1.savvis.net (208.172.131.82)  1106.382 ms sl-yahoo3-23-0.sprintlink.net (144.228.250.78)  1183.981 ms  1145.006 ms
9  216.39.64.3 (216.39.64.3)  1148.387 ms  1203.157 ms  1242.669 ms
10  p10.www.mud.yahoo.com (68.142.197.73)  1047.051 ms  977.461 ms secure.ern-inc.com (216.39.68.234)  1019.086 ms

Seems like TSTT is having uplink problems...

[R45]

Hmm, doing some more investigation... TSTT seems to be using new IP ranges. I got leased 201.238.76.221 which I can't remember every getting IPs in the subnet. I ran a traceroute from a server I have access to in the States to my IP, the output

Quote

traceroute to 201.238.76.221 (201.238.76.221), 64 hops max, 40 byte packets
1  supercomp-1.ext1.wdc.pnap.net (69.25.23.254)  0.388 ms  0.388 ms  0.363 ms
2  216.52.118.49 (216.52.118.49)  0.466 ms  0.312 ms  0.329 ms
3  core1.po2-bbnet2.wdc002.pnap.net (216.52.127.71)  0.352 ms  0.405 ms  0.350 ms
4  cpr1-gigabitethernet8-0.VirginiaEquinix.savvis.net (208.173.10.177)  0.349 ms  0.422 ms  0.228 ms
5  dcr1-so-6-1-0.Washington.savvis.net (208.173.52.114)  1.218 ms  1.278 ms  1.222 ms
6  bcs1-so-1-2-0-500.Washington.savvis.net (204.70.192.154)  15.101 ms  21.427 ms  24.454 ms
7  10.10.1.125 (10.10.1.125)  20.618 ms  31.775 ms  25.845 ms
8  acr1-so-7-0-0.Miami.savvis.net (204.70.193.189)  27.862 ms  27.646 ms  27.706 ms
9  bar1-loopback.Miami.savvis.net (208.172.98.3)  42.427 ms  27.752 ms  27.802 ms
10  tstt-ltd.Miami.savvis.net (208.172.100.202)  1271.967 ms  1317.293 ms  1316.080 ms
11  cuscon16451.tstt.net.tt (196.3.140.242)  1285.698 ms  1247.749 ms  1276.935 ms

Notice the major latency at tstt-ltd.Miami.savvis.net (The traceroute couldn't run completely because my firewall doesn't respond to pings). Whoever TSTT's new uplink provider is in Miami has serious problems.

Compare this to pinging TSTT's website, which is on their traditional subnet

Quote

traceroute to tstt.net.tt (196.3.132.8), 64 hops max, 40 byte packets
1  supercomp-1.ext1.wdc.pnap.net (69.25.23.254)  0.223 ms  0.219 ms  0.221 ms
2  216.52.118.49 (216.52.118.49)  159.833 ms  148.092 ms  0.852 ms
3  core2.ge1-1-bbnet1.wdc002.pnap.net (216.52.127.8)  0.365 ms  0.335 ms  0.351 ms
4  ge-3-3.a00.asbnva01.us.ra.verio.net (168.143.105.97)  0.353 ms  0.437 ms  0.357 ms
5  ge-1-1-0-4.r01.asbnva01.us.bb.verio.net (129.250.26.126)  75.066 ms  0.452 ms  0.470 ms
6  p16-1-0-0.r21.asbnva01.us.bb.verio.net (129.250.5.21)  39.699 ms  0.451 ms  0.482 ms
7  p16-0.sprint.asbnva01.us.bb.verio.net (129.250.9.54)  0.604 ms  0.579 ms  0.484 ms
8  sl-bb26-rly-6-0.sprintlink.net (144.232.20.135)  2.103 ms  2.299 ms  2.115 ms
9  sl-bb25-rly-13-0.sprintlink.net (144.232.14.169)  2.335 ms  2.668 ms  2.600 ms
10  sl-bb21-rly-11-0.sprintlink.net (144.232.14.157)  2.478 ms  2.167 ms  2.354 ms
11  sl-bb21-atl-6-0.sprintlink.net (144.232.20.176)  18.602 ms  18.166 ms  19.691 ms
12  sl-bb20-orl-14-0.sprintlink.net (144.232.20.124)  29.216 ms  29.287 ms  29.196 ms
13  sl-gw8-orl-0-0.sprintlink.net (144.232.2.225)  28.941 ms  28.884 ms  28.970 ms
14  sl-telec1-2-0.sprintlink.net (160.81.138.254)  92.027 ms  89.827 ms  88.750 ms
15  route.tstt.net.tt (209.94.205.6)  87.297 ms  89.327 ms  87.380 ms

I've email support and am awaiting a response.

[R45]

Am I the only one getting this? It's happening to me every day from around 5:30PM to 11:30PM (Peak time). I still get technically full down speeds, but there's atleast a 1000ms ping to anywhere during these times.

[srnoth]

Hi there,

Um, I don't know if this is related to what you are talking about, but something strange has been happening recently. About a week ago I found that the interntet was moving very slow, and so I ran TSTT's bandwidth test. It cam up with 260kbps which is about what I would normally get. Odd, I thought, so I ran a bandwidth test from somewhere else (I think it was bandwidthplace.com), and it came up with 45kbps!!

That's more like how it felt. It seems that TSTT was having problems with their uplink to the rest of the world. I guess that is what you were talking about.

Anyway, it seems to be working fine now, so I guess they figured it out.

[R45]

I took the liberty of contacting TSTT's uplink, SAVVIS Communications (http://www.savvis.net). I provided traceroute information, both outgoing and incoming. Initially, they replied testing it saying they noticed no latency. However, I followed up asking them to test during our peak periods (5:30PM to 11:30PM EST time). This is their latest reply:

Quote

Hi,

At this point I would recommend you contact TSTT in regards to the
latency. I am not able to open any tickets unless contacted directly by
TSTT. Please contact TSTT and have them contact us on this issue and we
will be happy to assist.

Thanks.

The above implies, atleast to me, that they've noticed the problem. Of course, TSTT is their customer, we are only at the end of the chain. I called TSTT and was told it was due to spyware on my computer.... I'm really interested to know how a traceroute FROM an external server TO my network which shows latency before it even reaches my router could be attributed to "Spyware", or anything to do with me for that matter.

Anyone have any ideas on getting TSTT to actually check their network?

[Wolfie]

I get horrible ping times during the day, EVERYDAY.

[R45]

Wolfie, on Apr 15 2005, 10:43 AM, said:

I get horrible ping times during the day, EVERYDAY.

It seems to have deteriorated to any time of the day now. Is your IP by chance in the 201.238 class B network?

[Wolfie]

nah 200.108 C. Just tried to go on a battlefield server again, got kicked for high ping

[R45]

Wolfie, on Apr 15 2005, 10:56 AM, said:

nah 200.108 C

I've stopped being leased those IPs for the last week. Ever since I started getting 201.238 addresses, I've been having the (recent, the regular problems were always there) major problems.

Right now I'm awaiting a call from "Someone in that department", atleast they acknowledge it isn't spyware on my computer

[Wolfie]

More than likely they cap bandwidth per exchange. More than likely they do not update those limits regularly. See where this is going?

[R45]

My issue is not really to do with exchange caps. From the traceroutes, it appears to be network latency with TSTT's uplink to Miami for this specific route.

[Wolfie]

tonight i got one of the ips you mentioned and yes it was crawling. i just logged out and back in till i got a "normal" ip again and everything was fine.

[srnoth]

It's Monday night (April 25th) and I got one of the dreaded 201.238.*.* IP address. It's as slow as a tortoise, I measured 50kbps at bandwidthplace.com. *#*(#($#&%$&$&!!!! If I wanted dialup I would have paid a lot less. As I expected, I scored a full 270kbps on TSTTs bandwidth test, which I guess confirms that it is a problem with TSTT's provider. ARG!!!!!

Anywho, for now I guess I will just keep rebooting the modem till I get a better IP address.


Laterz,

[srnoth]

Yay!! I got back a normal IP address. Full speed ahead!!!


Laterz,
Stephen.

[Wolfie]

this is my traceroute tonight:


traceroute to cuscon13***.tstt.net.tt (200.108.**.**), 30 hops max, 38 byte packets
1 ev1s-207-44-134-1.ev1servers.net (207.44.134.1) 0.346 ms 0.281 ms 0.257 ms
2 ivhou-207-218-245-7.ev1.net (207.218.245.7) 0.467 ms 0.384 ms 0.337 ms
3 ivhou-207-218-223-5.ev1.net (207.218.223.5) 0.402 ms 0.389 ms 0.390 ms
4 ge-1-1-0.r02.hstntx01.us.bb.verio.net (129.250.10.65) 1.104 ms 1.199 ms 1.032 ms
5 p16-1-0-1.r20.dllstx09.us.bb.verio.net (129.250.5.40) 8.849 ms 8.954 ms 8.878 ms
6 sl-st20-dal-14-2-1620xT1.sprintlink.net (144.232.8.121) 45.502 ms 215.521 ms 62.195 ms
7 sl-bb27-fw-5-0.sprintlink.net (144.232.9.137) 133.970 ms 203.758 ms 12.738 ms
8 sl-bb24-fw-14-0.sprintlink.net (144.232.11.73) 9.445 ms 39.434 ms 207.708 ms
9 sl-bb22-orl-2-0.sprintlink.net (144.232.9.36) 41.587 ms 41.616 ms 41.304 ms
10 sl-bb21-orl-13-0.sprintlink.net (144.232.2.149) 49.008 ms 45.591 ms 45.717 ms
11 sl-gw8-orl-0-0.sprintlink.net (144.232.2.225) 41.028 ms 42.092 ms 41.283 ms
12 sl-telec1-1-0.sprintlink.net (160.81.34.246) 321.657 ms 322.518 ms 326.773 ms
13 * tservq.tstt.net.tt (209.94.205.25) 279.263 ms 316.015 ms
14 cuscon13***.tstt.net.tt (200.108.**.**) 342.572 ms 374.886 ms *