Exactly one endpoint (tserv7.ash1 at Ashburn, VA, US) is shown as "down" on https://www.tunnelbroker.net/status.php now. How do your traces over the tunnel compare to similar traces via http://lg.he.net ? Jitter aside, mine is solid in Dallas (at least to/fro' Google)... 2. ge6-22.core1.dal1.he.net 0.0% 18 95.1 39.1 16.7 173.5 40.3 3. 10ge5-4.core1.atl1.he.net 0.0% 18 195.0 63.5 37.7 195.0 41.6 4. 2001:4860:1:1:0:1b1b:0:15 0.0% 18 140.2 53.7 36.9 142.1 32.9 5. 2001:4860::1:0:489 0.0% 18 46.9 52.4 36.7 146.1 24.9 6. 2001:4860::8:0:52bb 0.0% 18 65.0 60.9 38.2 121.1 30.6 7. 2001:4860::8:0:2c9d 0.0% 18 55.6 65.9 55.2 131.3 21.2 8. 2001:4860::1:0:dd7 0.0% 18 57.9 74.8 56.0 156.1 30.4 9. 2001:4860:0:1::f9 0.0% 18 56.6 63.6 55.1 158.0 23.7 10. dfw06s33-in-x00.1e100.net 0.0% 18 58.1 74.2 55.8 192.5 39.7 On Wed, 2014-08-27 at 19:10 +0000, Matthew Huff via Outages wrote:
My BGP session to HE for IPv6 has bounced twice in the last few minutes. It's been stable for years, so something is going on.
Traceroutes to the IPv4 tunnel destination get from lightpath to HE, but appear to get lost in HE.
Anyone know what's going on?
---- Matthew Huff | 1 Manhattanville Rd Director of Operations | Purchase, NY 10577 OTA Management LLC | Phone: 914-460-4039
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages