Re: ATT NOC

We're not accepting the route from our peers due to the AS-SET in the path: 174 199659 {65002}, (aggregated by 199659 10.10.10.3), (received-only) 2914 199659 {65002}, (aggregated by 199659 10.10.10.1), (received-only) On Tue, Oct 10, 2017 at 12:35 PM Gavin Henry

Re: ATT NOC

Please provide source and destination. On Tue, Oct 10, 2017 at 12:22 PM Gavin Henry wrote: > Hi all, > > For a while now (11 days) we've been trying to reach ATT as it some of > our traffic is dying within their network. It's traffic destined for > their customer networks

Re: ATT NOC

Hi all, In an effort to embarrass myself and let someone else stumble across this, I did not have remove-private on our transit sessions and AS65002 leaked out. It seems Cogent removed it though. NTT and Level3 trusted us. I've added this to those groups and peering groups. Really appreciate the

Re: ATT NOC

On 10 October 2017 at 17:47, Nimrod Levy wrote: > We're not accepting the route from our peers due to the AS-SET in the path: > 174 199659 {65002}, (aggregated by 199659 10.10.10.3), (received-only) > 2914 199659 {65002}, (aggregated by 199659 10.10.10.1), (received-only)

Re: ATT NOC

Hi Nimrod, Sorry. Our resolvers that are having the issue live at: 185.8.92.12 185.8.92.13 part of 185.8.92.0/22 Destination IP's we're trying to reach are: dns4.hertz.com has address 12.5.245.250 dns5.hertz.com has address 12.147.231.250 dns6.hertz.com has address 12.28.81.250 These live

ATT NOC

Hi all, For a while now (11 days) we've been trying to reach ATT as it some of our traffic is dying within their network. It's traffic destined for their customer networks so we can't raise a ticket with ATT directly. We've emailed their NOC, but nothing and since then been trying to raise tickes