<.< >.> Huh, my network seemed to glitch out for a bit there. just to arp, or in general? My ssh to ARP timed out (on a call so can't dig into it) ahh (and I tried reconnect and it timed out) that's even more disconcerting heh For all I know, it was my home IPv4 or v6 connection Though Smokeping suggests it was ARP-side... Looks like HE's v6 routing is b0rked, mtr from my home to my VPS' v6 address gets stuck at 10ge13-4.core1.sjc2.he.net Or maybe not HE, mtr from my VPS back to my home v6 address is going over ntt.net and gets stuck at ae-40.r02.snjsca04.us.bb.gin.ntt.net asymmetric routing \o/ http://sprunge.us/bBUY to clarify Yep, and asymmetric routing is fine... as long as it works :p i'd suspect he.net over ntt normally but from that mtr you can't really tell where it's going wrong tcpdump shoudl be able to tell you if it passes traffic in one directoin Sorry :) Oh yeah, sure arp can't reach www.he.net atm Confirmed my home->vps ping was received at the vps, and replied to (haven't tcpdump'd my end of the HE tunnel) yeah mtr to he gets stuck in ntt.net (And confirmed, no response received at my end of the tunnel) So... blaming ntt yaeh or ntt to he.net is it working better now? Yes! (I see you, or someone, changed the return route) me he.net was dropping out before though, let's hope it doesn't now :) it's still a mystery why ntt->he.net would suddenly break I know, let's switch to Cogent! /s (I assume Cogent/HE still haven't kissed and made up) yeh don't think so ntt's looking glass suggests it goes ntt -> telia -> he.net so it maybe it didn't failover very quickly the AS path length is still saying 2914 6939 (ntt he.net) err minus length :) oh ntt is down again now though mercutio: Thank you very much for the quick response :) you're welcome but i'm still curious what happened :)