AT&T explains why it blocked Cloudflare DNS: It was just an accident

Re:AT&T explains why it blocked Cloudflare DNS: It was just ... by tptacek on Friday May 04, 2018 @01:46PM (#16996566)

I've had better service from U-Verse and, more recently, AT&T Fiber than I have from Comcast.

But really, the point this thread is making isn't about whether you approve of all of AT&T's business decisions, but rather whether their backbone engineers can properly manage a network.

I'm interested in the opinions of people who have managed default-free BGP peering before on whether AT&T does a good job, but I'm not so much interested in reading another dslreports thread about whether AT&T is a "good ISP".

[ Parent | on HN ]

Re:AT&T explains why it blocked Cloudflare DNS: It was just ... by mjcl on Friday May 04, 2018 @02:22PM (#16996940)

My experience with AT&T was that they were overly bureaucratic but outside of those rules anything goes. For example, they didn't ask for an LOA for BGP announcements of other people's IP space. When we were turning up a new Comcast circuit we accidentally leaked Comcast's customer routes (~5000) to AT&T and they were accepted.

[ Parent | on HN ]

Re:AT&T explains why it blocked Cloudflare DNS: It was just ... by supertrope on Friday May 04, 2018 @01:53PM (#16996649)

This technical glitch is in their CPE boxes not the backbone network.

[ Parent | on HN ]

Re:AT&T explains why it blocked Cloudflare DNS: It was just ... by tptacek on Friday May 04, 2018 @01:56PM (#16996681)

Good to know! Add to the set of people who's AT&T network engineering opinions are interesting "anyone who has managed a very large scale distribution layer network". :)

[ Parent | on HN ]