cds222
@rr.com
| San Diego - Routing change
Background: I commute back and forth to China for a startup and telecommute from San Diego when I'm not overseas. My DSL Extreme 6/768 ADSL line has been perfect for my Site-Site VPN connections because I have been able to get 200-220ms latency to my remote endpoint. I also have a TW cable line (15/2) for general Internet stuff, but route everything China-related over the ADSL line since my TW latency was averaging 500-600ms.
So I woke up this morning and noticed my VPN tunnels were down and I thought it was most likely due to a DHCP renewal that gave me a different IP - not usually a big deal. I just have to change the remote endpoint config to reflect my new IP and I'm usually off and running. First thing I notice is that the new IP given out by the DSL Extreme DHCP server is on an entirely different netblock - odd, but not entirely unusual. However, after I change the remote endpoint config and the tunnels start popping back up I notice my latency is around 500-600ms. First thing I check is the routing to make sure I'm still sending the tunnel over the ADSL line and haven't for some reason reverted to the default route of the TW line (even though the tunnels wouldn't have established otherwise since it would have sourced from my TW line which was unknown to the remote endpoint). Nope, still going over the ADSL line.
So now I do a traceroute and notice that DSL Extreme is now sending my over an ATT peer in LA and then up to SF then out across to China. IIRC I used to be sent over an L3 peer and then out to China, but I'm not 100% positive. What I do know however is that I'm now seeing much higher latency that what I was seeing last night.
I then call DSL Extreme and speak to one of their L1 support techs and he confirms there was indeed maintenance on my area early this morning and said it was entirely possible that they re-routed our area through another peer in order to save money - apparently they're in the process of cost cutting and are consolidating peering arrangements, but he did say he couldn't be 100% positive since that type of info was beyond his capabilities. Just to be sure he's going to have a level 2 tech call me back.
Has anybody else had any issues with latency in the San Diego area this morning? Although I think I'll be hard-pressed to find anyone else down here with a similar setup/requirements, I thought I'd toss this out to the forum and see if I got lucky. |
|
dslx_gm
Premium,VIP
join:2002-12-26
Winnetka, CA | Can you please provide a trace route so we can take a look?
Thanks |
|
cds222
@rr.com
moderated:
April 9th, @01:46PM
| Okay, very strange - now my Juniper ADSL interface grabbed an IP off the netblock I was on up until the network changes this morning:
However, I'm still seeing much higher latency than I was just last night. I swear, I was averaging 200-220ms up until this morning! ;)
Unfortunately I don't have any saved traceroutes from pre-changes.
I'm wondering if the L1 tech was accurate in stating that they did indeed change peering as part of this morning's network changes - like I said in the original post, I am fairly certain I wasn't going through an ATT peer when hopping over to CZ.
[Mod edit: fixed the blown out margins. sash] |
|
cds222
@rr.com
| reply to dslx_gm
Not sure what's going on but I'm seeing better results:
Closer to my previously-seen (consistent) 200-220ms, but not quite there yet.
One thing I've gotten used to is the rapid increase in latency when the Chinese start their day - most days that ends up being ~4-6pm Pacific, after which time all bets are off. We are involved with Guangzhou Telecom and I've learned that they shape their bandwidth based on time-of-day (that and the fact that usage naturally increases locally when their day starts).
BTW, thanks sash for the formatting edit - I didn't notice the code tag when I first posted. |
|
sashwa
Pixie Cat Crunches and Folds
Premium,Mod
join:2001-01-29
Alcatraz
clubs:  | Not a problem. The pre tags always blow my margins out.  |
|
cds222
@rr.com
|  reply to cds222
Well, all is well now - in fact, better than I usually see. Not sure what the exact problem was but the peer is now quite speedy and I'm back in business.
The DSLX network maintenance in my area early this morning and the increased latency might have indeed been a coincidence. Either way, I'm not going to question it ;)
Also want to point out that I just received a call from (L2?) support @ DSL Extreme and the gentleman was great - even gave me instructions on how to quickly escalate similar issues in the future.
|
|
