AT&T U-Verse Blocking traffic on (Again?)

DNS Server is ok:

$ dig @ +short

DNS Server is unresponsive:

$ dig @

; <<>> DiG 9.10.6 <<>> @
;; global options: +cmd
;; connection timed out; no servers could be reached

HTTPS is also blocked:
$ curl --head
curl: (7) Failed to connect to port 443: Connection refused

HTTPS on is ok:
$ curl --head
HTTP/2 200
date: Wed, 21 Nov 2018 17:11:26 GMT
content-type: text/html
last-modified: Thu, 15 Nov 2018 02:54:12 GMT
strict-transport-security: max-age=31536000; includeSubDomains; preload
cache-control: max-age=600
x-content-type-options: nosniff
expect-ct: max-age=604800, report-uri=“
server: Cloudflare
cf-ray: 47d4c6892c9aba78-ATL

Traceroute resolves incorrectly:

$ traceroute
traceroute to (, 64 hops max, 52 byte packets
 1 (  2.229 ms  1.205 ms  0.993 ms
 2 (  2.345 ms  1.864 ms  1.705 ms

$ traceroute
traceroute to (, 64 hops max, 52 byte packets
 1 (  3.110 ms  1.618 ms  1.186 ms
 2 (  2.041 ms  1.861 ms  1.814 ms
 3 (  29.172 ms  22.802 ms  34.993 ms
 4 (  24.747 ms  28.078 ms  23.434 ms
 5 (  24.744 ms * *
 6 (  26.656 ms (  25.386 ms  24.526 ms
 7 (  30.676 ms  33.010 ms  31.229 ms
 8 (  30.014 ms  29.280 ms  29.730 ms
 9 (  29.330 ms  34.309 ms  31.055 ms
10 (  29.730 ms  29.970 ms  29.746 ms

For what it is worth, I’m also unable to connect to But is ok. But that is not relevant to this forum.

Quick update: AT&T has fixed the routing issue to But is still blocked for me. works.

It would seem as if your own network hardware hijacks

What is and what is is my personal router and is the AT&T supplied router.

My guess would be the AT&T router hijacks the address in this case. Which model is it?

It is an AT&T branded box. The diagnostics say:

Manufacturer: Pace Plc
Model: 5268AC

That seems to be identical to the Arris 5268ac.

There is quite a bit on that out there, also here on the forum FYI: Not working with AT&T U-Verse

Maybe can help too, or

Interesting. Thanks for the information. It looks like there is nothing I can do to fix it. I’ll just use for now.

For completeness, I tried running a traceroute directly from the router using the web interface on the router. Here is the result:

To (good):

traceroute with: 64 bytes of data

1:, time=20 ms
2:, time=23 ms
3:, time=23 ms
4:, time=23 ms
5:, time=28 ms
6:, time=26 ms
7:, time=39 ms
8:, time=31 ms

And to (bad):

traceroute with: 64 bytes of data

1:, time=0 ms

In one of the articles someone mentioned a possible patch being released by AT&T to address that issue. Maybe check if there is such a patch available. You have to use their router I presume, right? Its the DSL modem, isnt it?

I just checked mine and it is working now tracerouting to is the same as

Looks like my DSL modem was rebooted 9 days ago.

Current firmware is

I have the same pace modem BTW


The AT&T router (as the dslreports links mention) is using for some internal routing. It seems some updates have fixed this, but broken other things. The current workaround is to bypass the router with another box that’s forwarding the ethernet authentication pings to the router. Otherwise, the router isn’t handling any traffic. It’s ridiculous. This is also for their 1 Gig fiber products, I imagine they share modems to some extent.

Yes. That is correct.

Nice. Mine is still at Hopefully I’ll get the 11.1 update pushed to my router soon and that will fix the issue for me.

You might be able to manually install it if you like: