Greetings,

I't been quite a while now... since my last post here. This is certainly due to the fact that I never been so well hosted (SM) and server managed (LNC). SM network is so stable. I sleep so much better now (since 6 months) that I am here

Well... Today I am posting because I am in need for SM Network Staff help me pinpoint and localize where could be my connexion's problem to SM...? Wish I could have lower PINGS like they were a month ago (~60ms), with less HOPS

Here's the info I gathered regarding this:

My cable ISP here in Québec, Canada, is Videotron.

My REMOTE IP address: 69.70.93.85
My SERVER'S IP address: 69.93.196.132

SERVER --> REMOTE
--- 69.70.93.85 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99166ms
rtt min/avg/max/mdev = 88.563/91.319/113.959/3.783 ms, pipe 2

REMOTE --> SERVER
--- 69.93.196.132 ping statistics ---
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max = 89.736/93.126/114.714 ms

Addon info:


Thank you for looking into this

Yves

The problems seems to be within Sprint network way before it hits SM/TP network.

I actually now wish that ServerMatrix would open up their Cogent line to all servers.

My ISP switched over to Cogent as their primary carrier, so my route looks like:

iStop (My ISP)
Cogent
Gblx
ThePlanet

Gblx is only two hops, but a lot of latency seems to be adding on inside of dallas from the ISP switches in there.

Considering how many smaller ISPs probably use Cogent for transit, I think if SM were to get a second Cogent line (Perhaps just a 100mbit one) to route data from users who have Cogent transit from their ISP, it'd help a lot of people reduce their latency.

The problem appears to be the return path to you (via Broadwing):

traceroute to modemcable085.93-70-69.mc.videotron.ca (69.70.93.85): 1-30 hops, 38 byte packets
1 beastie-gw.theplanet.com. (12.96.160.73) 0.269 ms 0.186 ms 0.174 ms
2 ibr2-ae0-v1.dllstx2.theplanet.com (12.96.160.2) 0.258 ms (ttl=253!) 0.232 ms (ttl=253!) 0.270 ms (ttl=253!)
3 67.99.43.233 (67.99.43.233) 0.291 ms (ttl=252!) 0.302 ms (ttl=252!) 0.290 ms (ttl=252!)
4 p2-1.c0.ftwo.broadwing.net (216.140.4.225) 0.953 ms 0.939 ms 0.924 ms
5 p3-0.a0.lsan.broadwing.net (216.140.4.1) 30.4 ms P4-2.a0.hywr.broadwing.net (216.140.2.9) 30.5 ms 30.4 ms
6 so-0-0-0.a1.lsan.broadwing.net (216.140.2.110) 30.7 ms (ttl=249!) 30.5 ms (ttl=249!) 30.5 ms (ttl=249!)
7 if-7-8.core1.LosAngeles.Teleglobe.net (207.45.193.69) 30.4 ms (ttl=246!) 30.3 ms (ttl=246!) 30.5 ms (ttl=246!)
8 if-5-0.core2.LosAngeles.Teleglobe.net (207.45.223.61) 79.5 ms (ttl=239!) 79.7 ms (ttl=239!) 79.5 ms (ttl=239!)
9 if-5-0.core3.NewYork.Teleglobe.net (64.86.83.173) 79.4 ms (ttl=240!) 79.6 ms (ttl=240!) 79.7 ms (ttl=240!)
10 if-4-0.core2.NewYork.Teleglobe.net (66.110.8.138) 72.5 ms (ttl=243!) 72.6 ms (ttl=243!) 72.3 ms (ttl=243!)
11 if-2-0.core1.Montreal.teleglobe.net (66.198.81.13) 90.5 ms (ttl=242!) 79.5 ms (ttl=242!) 79.5 ms (ttl=242!)
12 ix-10-2.core1.Montreal.teleglobe.net (66.198.81.10) 79.7 ms (ttl=240!) 79.7 ms (ttl=240!) 79.9 ms (ttl=240!)
13 * * *
14 * * *
15 24.200.250.98 (24.200.250.98) 83.2 ms (ttl=239!) 101 ms (ttl=239!) 83.3 ms (ttl=239!)
16 24.200.234.153 (24.200.234.153) 83.2 ms (ttl=237!) 83.2 ms (ttl=237!) 82.9 ms (ttl=237!)

Going from Dallas - to LA - back to NY.

Lemme see what moving the routes does:

traceroute to modemcable085.93-70-69.mc.videotron.ca (69.70.93.85): 1-30 hops, 38 byte packets
1 beastie-gw.theplanet.com. (12.96.160.73) 0.289 ms 0.203 ms 0.215 ms
2 ibr2-ae0-v1.dllstx2.theplanet.com (12.96.160.2) 0.255 ms (ttl=253!) 0.305 ms (ttl=253!) 0.329 ms (ttl=253!)
3 sl-st1-dal-2-1.sprintlink.net (144.228.250.113) 0.398 ms (ttl=252!) 0.399 ms (ttl=252!) 0.609 ms (ttl=252!)
4 144.232.29.99 (144.232.29.99) 0.743 ms 0.560 ms 0.754 ms
5 sl-bb20-fw-13-0.sprintlink.net (144.232.20.16) 2.01 ms 2.07 ms 1.77 ms
6 sl-bb21-fw-14-0.sprintlink.net (144.232.11.218) 2.09 ms 2.12 ms 1.95 ms
7 sl-bb21-chi-6-0.sprintlink.net (144.232.8.53) 22.2 ms 21.9 ms 22.2 ms
8 sl-bb22-nyc-15-0.sprintlink.net (144.232.9.148) 43.8 ms 43.8 ms 43.7 ms
9 sl-bb26-nyc-11-0.sprintlink.net (144.232.7.41) 44.0 ms 43.8 ms 43.8 ms
10 sl-bb27-nyc-8-0.sprintlink.net (144.232.7.38) 43.8 ms 44.1 ms 43.7 ms
11 sl-gw31-nyc-1-0.sprintlink.net (144.232.13.34) 43.8 ms 43.5 ms 43.6 ms
12 sl-teleg-1-0.sprintlink.net (160.81.249.30) 43.9 ms 43.6 ms 43.7 ms
13 if-4-0.core2.NewYork.Teleglobe.net (66.110.8.138) 44.0 ms 43.9 ms 44.0 ms
14 if-2-0.core1.Montreal.teleglobe.net (66.198.81.13) 50.9 ms 50.8 ms 50.9 ms
15 ix-10-2.core1.Montreal.teleglobe.net (66.198.81.10) 51.1 ms (ttl=240!) 51.6 ms (ttl=240!) 51.2 ms (ttl=240!)
16 * * *
17 * * *
18 24.200.250.98 (24.200.250.98) 54.5 ms (ttl=239!) 54.2 ms (ttl=239!) 54.5 ms (ttl=239!)
19 24.200.234.153 (24.200.234.153) 54.2 ms 54.2 ms 54.3 ms

That better?

Better? Looks like it

Sorry William
I don't quite understand...
I get better PINGS (61 ms) now... altough... the route seems to be the same

Thanks,

Yves

Your route to us is the same, the route the packets take back to you is different now.

Routing on the Internet is asymmetric - your packets don't usually take the same path back to you that they do from you. I identified a bad routing path back to you and re-routed traffic to your IP (actually your ISP) through an alternate provider that had a better path back to you.

Hope this explains things.

Awesome! It sure does explain very well now
Thank you again William for your good work and transparency (thumbs up!)

Sincerly,

Yves

What software is that?

Looks like Visualroute http://www.visualware.com/personal/product...oute/index.html

Exactly Edwin ! VisualRoute
And... I could not go without anymore.
It's always awesome to see all this info

Take care

Yves

I'd like to know what William thinks of getting some Cogent connectivity into the general mix for those of us with Cogent-powered ISPs. Maybe set up a router on the current Cogent connection to route over the interconnect to our normal servers?

It's not likely to happen soon. The stigma surrounding Cogent is still too recent to take that leap right now (whether it is deserved or not).