For what it's worth, we've been told by nlayer that there is some type
of outage here. We've switched traffic over to Level 3 instead, and the
servers are back in the pool.
On 8/29/2014 1:59 PM, staticsafe wrote:
On 8/29/2014 10:57, Brian Rak wrote:
Is anyone else seeing IPv6 connectivity issues to the monitoring server?
It looks somewhat like a nLayer issue to me.
Traceroutes don't get very far from the monitoring server before they die.
nLayer's LG is showing a route:
BGP routing table entry for 2001:19f0::/38
AS-PATH: AS path: 20473
AS-PATH Translation: AS-CHOOPA
Active Path (*)
Local Preference: 300
MED: 50
IGP cost: 0
Last updated: 1d 0:41:00
Learned from: lo0.cr1.ewr1.us.nlayer.net (69.31.95.248)
Protocol Nexthop: as20473.ae7.ar2.nyc3.us.nlayer.net
(2001:590::451f:224e)
Communities: 4436:41312
Internal Communities:
Relationship: Customer (4)
Continent: North America (1)
Region: North East (3)
City: New York NY, US (NYC)
This is where another looking glass dies on me:
4. xe-11-3-0-304.cr1.nyc2.us.nlayer.net 0.0% 10 0.6 0.6 0.6
0.7 0.0
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
