Ridiculous latency, started last night

[kaev]

Dunno what's up with all the lightower.net hops, disturbed that there is a broken hop in the middle of that.


C:\Users\tony>tracert project1999.com

Tracing route to project1999.com [144.121.19.170]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms modem.domain [192.168.0.1]
2 15 ms 4 ms 4 ms 67-4-192-254.mpls.qwest.net [xxx.xxx.xxx.xxx]
3 5 ms 9 ms 5 ms stpl-agw1.inet.qwest.net [207.109.3.129]
4 6 ms 5 ms 3 ms 4.68.38.177
5 51 ms 50 ms 54 ms ae-2-3611.edge2.NewYork6.Level3.net [4.69.209.82]
6 50 ms 53 ms 51 ms FIBERTECH-N.edge2.NewYork6.Level3.net [4.30.181.126]
7 59 ms 40 ms 38 ms ae3-nycmnyzrjp1.lightower.net [144.121.35.41]
8 38 ms 38 ms 38 ms ae2-bstpmalljp1.lightower.net [144.121.35.32]
9 * * * Request timed out.
10 1350 ms 38 ms 44 ms ae0-brtnmas6j81.lightower.net [65.254.31.58]
11 53 ms 37 ms 37 ms 144.121.7.234.lightower.net [144.121.7.234]
12 38 ms 37 ms 38 ms 144.121.19.170.lightower.net [144.121.19.170]

Trace complete.

[xaix1999]

so the trace route program is good for identifying problems on the route
not your latency
what is your ping results?
what was your latency issue on your server?

[Baler]

"Request timed out" can mean a few things, not always broken.

It could mean that the device is configured to not respond to you.
Or the destination's firewall is blocking the request.
It could mean that it's actually a bad hop and has to be re-routed.
Or it could mean there is an issue with the return path. (takes to and from in order to get the number)

[xaix1999]

so you can pick apart this trace route but there is nothing here
light tower is the business complex that holds p99 servers
they have an infrastructure (which I'm surprised responds at all)
when i setup my network topology first thing i configure is drop all pings as that's a good way for bad people to map your network layout
please provide more information about your latency issue
if you still have it, let us know, I'm sure it's already cleared up