mnathani_: next step figure out how to use vrf so the routes dont end up in the routing table mercutio: it's mostly the muggyness kellytk: For anyone up to a challenge, find a VPS provider with a Seattle POP that my pathetic ISP doesn't route through CA mercutio: amazon mnathani_: CA as in california or Canada kellytk: California mercutio: ahh i didn't even think of that mnathani :)
i assumed he meant california mnathani_: whats your location / ISP? kellytk: A lot of traffic goes through Vancouver it was a fair question mercutio: yeah he had a good point that i'd missed mnathani_: :-) kellytk: I should have been more specific. Re: location Seattle and it's going through sttl.wa.frontiernet.net mercutio: your isp is frontiernet? kellytk: For 8/9 providers it went as far south as snjsca04.us.bb.gin.ntt.net before returning from its long and circuitious journey mercutio: but what's your isp
that's what matters :/
for what upstreams they have
for all we know your isp sends all of it's traffic to seattle normally
mm, steam have servers in seattle
is that direct? kellytk: I haven't tried AWS mercutio: try tracing sea.valve.net
it just might help you check how your isp is routing
but going down to california isn't extreme
it's 15 msec from san jose to seattle?
it's not like it's going to new york or something :/ kellytk: I wouldn't be looking for alternatives but I'm getting ~300ms pings to every VPS host mercutio: and even with the accumulative nature of latency 15msec isn't likely to make much difference when you're that close.
that sounds like congestion
what ping do you get to arp?
my friend was getting better pings to los angeles than san jose when living in santa clara..
because of congestoin kellytk: BTW pings to sea.valve.net come back at ~30ms mercutio: congestion even
that seems high kellytk: Trace dies at ae11.mpr2.sea1.us.zip.zayo.com mercutio: weird i can trace all the way through kellytk: ~58ms pings to my Arp host
Literally 1/5 of pings to VPS providers in my own city mercutio: is your arp route going over level3?
well 5 to 25 msec doesn't make difference to ssh ime kellytk: ge-100-0-0-13.r00.lsanca07.us.ce.gin.ntt.net jumps to vl5.s1.lax.arpnetworks.com mercutio: unless you're on a threshold, like 140 to 160 can make a difference kellytk: Again, if this was < 150 I wouldn't give it a second thought, but it's slower than 1994
28,8 bro, mad binaries mercutio: do what i did, get a low latency monitor :) kellytk: This is insulting
By monitor don't tell me you mean display? :-D mercutio: yes kellytk: Haha alright no more pints for mercutio! mercutio: if you use two monitors cloning each other you can show the time and compare latency
4.2.2.1 probably has a local node too
you may be able to change isp's and reduce latency by 20 msec or sch mnathani_: what was your isp again? mercutio: he said zayo i think?
oh didn't he also say frontier? kellytk: Yes mercutio: there's some frontier based in IN kellytk: AWS datacenter network test IPs are tough to find that's lame mercutio: i'm not sure what state that is kellytk: WA/Seattle mercutio: they're easy to find i think
what's your IP/
seattle is normal amazon west
i've got no idea why
most people host in east though anyway kellytk: If you can beat me to a URL with the answer I'll be impressed mnathani_: http://www.google.com kellytk: I'm saying the information is tough to find mnathani_: most answers can be found on that url mercutio: dynamodb.us-west-2.amazonaws.com
connecting in seattle with telia for me
so that should be ~30 too
and if so then 58 to arp seems normal kellytk: I'm saying it can't be found mercutio: i can mtr it fine
it doesn't show the last hop, but amazon stuff never does mnathani_: 77 ping for me from Toronto
goes straight from my isp to amazon mercutio: yeh everyone seems to optimise their transit to amazon
makes it good for testing, wouldn't recommend it for hosting though :) mnathani_: s/77/77msec BryceBot: <mnathani_> 77msec ping for me from Toronto ***: nathani1 is now known as nathani mercutio: oh i assumed you were in the west mnathani
dunno why :)
so you'd see 58 ping as good to arp? kellytk: I FOUND IT https://docs.aws.amazon.com/general/latest/gr/rande.html#ec2_region mercutio: and you probably have lots of traffic routing via new york kellytk: No mercutio: i gave you an address kelly kellytk: That wasn't what I sought, but rather documentation mercutio: what was your ping? kellytk: ec2.us-west-2.amazonaws.com nor us-west-2.amazonaws.com respond to ping, so I'm still without an answer mercutio: mtr it kellytk: What's that? mercutio: apt-get install mtr
or use pingplotter free if you're using windows kellytk: I can't justify installing something to evaluate a VPS host I'll find an alternative
I like to find really great small providers anyway
Thanks though mercutio: i thought you were trying to figure out your isp's routing
seattle has a peering exchange
and your isp is even on it
https://beta.peeringdb.com/ix/13
if you really wnat to find low ping that may help
but with a ping of 58 you shouldn't need to worry kellytk: Thanks for the pointer to peeringdb ***: toeshred has quit IRC (Quit: WeeChat 1.0.1)
toeshred has joined #arpnetworks
toddf has quit IRC (*.net *.split)
ant has quit IRC (*.net *.split)
dne has quit IRC (*.net *.split)
ant has joined #arpnetworks
toddf has joined #arpnetworks
ChanServ sets mode: +o toddf
dne has joined #arpnetworks
kellytk has left "WeeChat 1.0.1"
KDE_Perr1 is now known as KDE_Perry
ameise has joined #arpnetworks
ant has quit IRC (Ping timeout: 240 seconds)
ameise is now known as ant nathani: @weather yyz BryceBot: Toronto-Pearson International, Ontario: Mostly Cloudy ☁ 39°F (4°C), Humidity: 75%, Wind: From the ESE at 8 MPH -- For more details including the forecast and almanac, see http://www.wunderground.com/cgi-bin/findweather/getForecast?query=43.67722321,-79.63055420 or re-request this with: @weather -v yyz ***: mercutio has quit IRC (Read error: Connection reset by peer)
mercutio has joined #arpnetworks
mercutio is now known as Guest45413
Guest45413 is now known as mercutio
ChanServ sets mode: +o mercutio