dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
3755
Gren3
join:2015-01-01

Gren3 to justasomeone

Member

to justasomeone

Re: Dota 2 Routing issue with teksavvy

32 ping would be amazing.
TNZ2
join:2015-01-22

TNZ2 to Gren

Member

to Gren
Is there any update, or has anyone else experiencing this issue seen an improvement?

Still fairly consistently getting about 10 ms better ping to USE while situated in Calgary.

US West Tracert:
Tracing route to eat.valve.net [192.69.96.1]
over a maximum of 30 hops:

1 9 ms 9 ms 8 ms Zero-PC [0.0.0.0]
2 11 ms 8 ms 9 ms 198-48-144-1.cpe.pppoe.ca [198.48.144.1]
3 21 ms 22 ms 22 ms ae0_1508-bdr01-van.teksavvy.com [76.10.191.57]
4 28 ms 31 ms 31 ms provinceofbc-van-gw.peer1.net [64.69.85.73]
5 24 ms 23 ms 25 ms 10ge-xe-0-1-0.van-hc16e-dis-1.peer1.net [216.187.115.130]
6 * * * Request timed out.
7 104 ms 125 ms 103 ms ae11.mpr2.sea1.us.zip.zayo.com [64.125.31.94]
8 130 ms 108 ms 101 ms ae11.mpr2.sea1.us.zip.zayo.com [64.125.31.94]
9 * * * Request timed out.
10 * 111 ms * eat.valve.net [192.69.96.1]
11 111 ms 112 ms 113 ms eat.valve.net [192.69.96.1]

Trace complete.

US East Tracert:
Tracing route to gw.sea.valve.net [208.64.201.1]
over a maximum of 30 hops:

1 9 ms 9 ms 10 ms Zero-PC [0.0.0.0]
2 12 ms 9 ms 9 ms 198-48-144-1.cpe.pppoe.ca [198.48.144.1]
3 21 ms 25 ms 26 ms ae0_1508-bdr01-van.teksavvy.com [76.10.191.57]
4 30 ms 30 ms 31 ms provinceofbc-van-gw.peer1.net [64.69.85.73]
5 * * 30 ms 10ge-xe-1-3-0.van-hc16e-dis-1.peer1.net [216.187.88.217]
6 * * * Request timed out.
7 * * 106 ms ae11.mpr2.sea1.us.zip.zayo.com [64.125.31.94]
8 109 ms 141 ms 107 ms 128.177.117.130.IPYX-094067-002-ZYO.zip.zayo.com [128.177.117.130]
9 * 112 ms 118 ms 205.196.6.36
10 104 ms 108 ms 104 ms gw.sea.valve.net [208.64.201.1]

Trace complete.

Something's happening right before it arrives in Seattle...

jmck
formerly 'shaded'
join:2010-10-02
Ottawa, ON

jmck

Member

its probably the return route being complete shit and going all the way out east then back out west.
TNZ2
join:2015-01-22

TNZ2

Member

Click for full size
Hey jmck,

Do you know why the routing might change from time to time?

Every once in a blue moon (like once per month or two) I get sensible ping to the Valve servers. Last night seemed to be one of those days. I took a look at the route again and it looks like the attached pic.

Route reverted back to normal (as in my previous posts) with ~100 ping again this morning

Guspaz
Guspaz
MVM
join:2001-11-05
Montreal, QC

Guspaz to Gren

MVM

to Gren
Even your "good" traceroute is suspicious. You're in Vancouver, the server is in Seattle (480 km round trip), but you're going through San Jose, California (5,864 km round trip).

This is absurd routing. It's easy to understand why your latency is so variable, your packets are travelling twelve times farther than they need to.
TNZ2
join:2015-01-22

TNZ2

Member

Actually I live in Calgary. Based on what I've seen my packets usually go through Vancouver regardless of where I'm trying to get to.

Guspaz
Guspaz
MVM
join:2001-11-05
Montreal, QC

Guspaz to Gren

MVM

to Gren
TekSavvy's western PoP is in Vancouver, so it's normal for everything to go through it (unless they've got another PoP somewhere now, like how they got a second one here in Montreal to complement the Toronto one).

But it still doesn't make sense to route traffic between Vancouver and Seattle through San Jose.