# AT&T Fiber Internet Blocking Plex login

**URL:** https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776
**Category:** General Discussions
**Created:** [March 19, 2019, 9:52pm UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776 "2019-03-19T21:52:06Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![dpope123](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@dpope123](https://forums.plex.tv/u/dpope123)
#### Post date: [March 19, 2019, 9:52pm UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/1 "2019-03-19T21:52:06Z")

</div>

Hoping this isn’t just me. I’ve reset my AT&T gateway to defaults and tried multiple devices wired and wireless. But no matter what I can’t get [https://plex.tv](https://plex.tv). Specifically any request to [plex.tv](http://plex.tv) on port 443 times out when I’m on AT&T U-Verse fiber internet. Works fine on AT&T cellular network and on my Comcast internet. Only appears to be blocked on AT&T home internet.

Anyone else experiencing this?

---

<div class="post-metadata">

### Author: ![Zgle](https://avatars.discourse-cdn.com/v4/letter/z/848f3c/32.png) [@Zgle](https://forums.plex.tv/u/Zgle)
#### Post date: [March 19, 2019, 10:12pm UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/2 "2019-03-19T22:12:37Z")

</div>

Yes, started several hours ago… no answer yet

> [@Can't access plex.tv but working with proxy or VPN](https://forums.plex.tv/t/cant-access-plex-tv-but-working-with-proxy-or-vpn/389662):
>
> Hello guys! Since around 2 hours my server stop working, saying that It can be contacted. I figured it out that from ANY computer on my network I can’t access [plex.tv](http://plex.tv), but if I use proxy or vpn, on same browser I can see the webpage without problems. I have AT&T, everything seems to be working. I restarted router (pfsense), plex server (just in case). but seems that I can’t connect to [plex.tv](http://plex.tv) from my att connection. The error is connection timed out. I been blocked from [plex.tv](http://plex.tv)? may be isp bl…

---

<div class="post-metadata">

### Author: ![OttoKerner](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/ottokerner/32/10079_2.png) [@OttoKerner](https://forums.plex.tv/u/OttoKerner)
#### Post date: [March 19, 2019, 10:58pm UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/3 "2019-03-19T22:58:23Z")

</div>

Can you set a different DNS server? Try Google’s (`8.8.8.8`)

---

<div class="post-metadata">

### Author: ![dpope123](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@dpope123](https://forums.plex.tv/u/dpope123)
#### Post date: [March 19, 2019, 11:31pm UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/4 "2019-03-19T23:31:35Z")

</div>

I already don’t use AT&T DNS. The IPs for [plex.tv](http://plex.tv) resolve correctly, but they are all unreachable on port 443. All devices trying to connect to it time out.

---

<div class="post-metadata">

### Author: ![dpope123](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@dpope123](https://forums.plex.tv/u/dpope123)
#### Post date: [March 19, 2019, 11:31pm UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/5 "2019-03-19T23:31:57Z")

</div>

Yikes, at least I’m not the only one. Thanks for the link!

---

<div class="post-metadata">

### Author: ![scriptman](https://avatars.discourse-cdn.com/v4/letter/s/9fc29f/32.png) [@scriptman](https://forums.plex.tv/u/scriptman)
#### Post date: [March 20, 2019, 1:21am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/6 "2019-03-20T01:21:00Z")

</div>

Same here. AT&T are blaming it on a DSLAM server issue, but I’m not buying it.

---

<div class="post-metadata">

### Author: ![scriptman](https://avatars.discourse-cdn.com/v4/letter/s/9fc29f/32.png) [@scriptman](https://forums.plex.tv/u/scriptman)
#### Post date: [March 20, 2019, 1:40am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/7 "2019-03-20T01:40:33Z")

</div>

Are you still experiencing the same issue? I configured a VPN connection on my plex server as a workaround until the issue is resolved.

---

<div class="post-metadata">

### Author: ![Achilles](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/achilles/32/16864_2.png) [@Achilles](https://forums.plex.tv/u/Achilles)
#### Post date: [March 20, 2019, 1:48am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/8 "2019-03-20T01:48:21Z")

</div>

Can you run a tcptraceroute to port [plex.tv:443](http://plex.tv:443)?

---

<div class="post-metadata">

### Author: ![zackhow](https://avatars.discourse-cdn.com/v4/letter/z/a4c791/32.png) [@zackhow](https://forums.plex.tv/u/zackhow)
#### Post date: [March 20, 2019, 1:58am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/9 "2019-03-20T01:58:23Z")

</div>

Same here, below is the traceroute, removed some of my IPs.

[https://pastebin.com/Vb6zwA08](https://pastebin.com/Vb6zwA08)

I will say I have a 172.x.x.x IP from ATT and it looks like other services are having issues with that block.

> **[r/sysadmin - AT&T -\> Microsoft outage affecting 172.x public IP ranges](https://www.reddit.com/r/sysadmin/comments/b31j6l/att_microsoft_outage_affecting_172x_public_ip/)**
>
> 24 votes and 15 comments so far on Reddit

---

<div class="post-metadata">

### Author: ![Achilles](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/achilles/32/16864_2.png) [@Achilles](https://forums.plex.tv/u/Achilles)
#### Post date: [March 20, 2019, 2:06am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/11 "2019-03-20T02:06:14Z")

</div>

That’s highly unlikely.

---

<div class="post-metadata">

### Author: ![Achilles](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/achilles/32/16864_2.png) [@Achilles](https://forums.plex.tv/u/Achilles)
#### Post date: [March 20, 2019, 2:07am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/12 "2019-03-20T02:07:38Z")

</div>

Looks like the traffic blackholes after the Level3 EU hop.

---

<div class="post-metadata">

### Author: ![Samwiseg0](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/samwiseg0/32/24501_2.png) [@Samwiseg0](https://forums.plex.tv/u/Samwiseg0)
#### Post date: [March 20, 2019, 2:09am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/13 "2019-03-20T02:09:02Z")

</div>

I am on ATT Fiber and all is well. East Coast US.

```auto
# dig plex.tv

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7_5.1 <<>> plex.tv
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4141
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;plex.tv. IN	A

;; ANSWER SECTION:
plex.tv. 4	IN	A	52.31.211.151
plex.tv. 4	IN	A	52.18.254.79
plex.tv. 4	IN	A	54.154.198.3
plex.tv. 4	IN	A	52.50.215.159
plex.tv. 4	IN	A	54.171.147.115
plex.tv. 4	IN	A	52.16.101.236
plex.tv. 4	IN	A	52.50.147.131
plex.tv. 4	IN	A	54.171.218.244

;; Query time: 1 msec
;; WHEN: Tue Mar 19 22:08:18 EDT 2019
;; MSG SIZE rcvd: 164

```

---

<div class="post-metadata">

### Author: ![scriptman](https://avatars.discourse-cdn.com/v4/letter/s/9fc29f/32.png) [@scriptman](https://forums.plex.tv/u/scriptman)
#### Post date: [March 20, 2019, 2:09am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/14 "2019-03-20T02:09:05Z")

</div>

Well, whatever is happening, it’s on their end.

---

<div class="post-metadata">

### Author: ![scriptman](https://avatars.discourse-cdn.com/v4/letter/s/9fc29f/32.png) [@scriptman](https://forums.plex.tv/u/scriptman)
#### Post date: [March 20, 2019, 2:16am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/15 "2019-03-20T02:16:06Z")

</div>

I did a traceroute and received the exact same thing.

---

<div class="post-metadata">

### Author: ![Achilles](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/achilles/32/16864_2.png) [@Achilles](https://forums.plex.tv/u/Achilles)
#### Post date: [March 20, 2019, 2:16am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/16 "2019-03-20T02:16:34Z")

</div>

What are the first two octet values of your public IP?

[http://whatismyip.me/](http://whatismyip.me/)  
or  
[https://canyouseeme.org/](https://canyouseeme.org/)

---

<div class="post-metadata">

### Author: ![dpope123](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@dpope123](https://forums.plex.tv/u/dpope123)
#### Post date: [March 20, 2019, 2:49am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/17 "2019-03-20T02:49:53Z")

</div>

> [@scriptman](#):
>
> Same here. AT&T are blaming it on a DSLAM server issue, but I’m not buying it.

Definitely not a DSLAM issue. That’s a device that serves a neighborhood or large area. It’s also for DSL, not fiber.

---

<div class="post-metadata">

### Author: ![dpope123](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@dpope123](https://forums.plex.tv/u/dpope123)
#### Post date: [March 20, 2019, 2:50am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/18 "2019-03-20T02:50:47Z")

</div>

> [@Achilles](#):
>
> What are the first two octet values of your public IP?
> 
> [http://whatismyip.me/](http://whatismyip.me/)  
> or  
> [https://canyouseeme.org/](https://canyouseeme.org/)

172.1.x.x

---

<div class="post-metadata">

### Author: ![scriptman](https://avatars.discourse-cdn.com/v4/letter/s/9fc29f/32.png) [@scriptman](https://forums.plex.tv/u/scriptman)
#### Post date: [March 20, 2019, 2:51am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/19 "2019-03-20T02:51:22Z")

</div>

172.7.x.x

---

<div class="post-metadata">

### Author: ![Achilles](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/achilles/32/16864_2.png) [@Achilles](https://forums.plex.tv/u/Achilles)
#### Post date: [March 20, 2019, 2:59am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/20 "2019-03-20T02:59:39Z")

</div>

> [@dpope123](#):
>
> 172.1.x.x

> [@scriptman](#):
>
> 172.7.x.x

Someone somewhere along the way has inadvertently/advertnantly blocked public IP space in the 172.0.0.0/12 from passing traffic. This is not on your end nor Plex’s end. This is somewhere in the middle.

You will have to wait it out. Unfortunately this problem is going to be owned by a high level backbone network engineer that neither you or AT&T Customer support will have direct access to. It will have to be escalated. The good thing is that its not impacting just Plex users. It seems to be impacting Microsoft Office 365 users as well–so I am sure its already been escalated.

---

<div class="post-metadata">

### Author: ![tixetsal](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/tixetsal/32/185122_2.png) [@tixetsal](https://forums.plex.tv/u/tixetsal)
#### Post date: [March 20, 2019, 3:47am UTC](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776/21 "2019-03-20T03:47:03Z")

</div>

Some AS is probably misidentifying that traffic as RFC1918 address space via some fat-fingered ACL or fw rule…

[Next page](https://forums.plex.tv/t/at-t-fiber-internet-blocking-plex-login/389776.md?page=2)
