Plex was down on Tuesday, and some users could not reach their own media even on the same home network where it was stored. The problem was not limited to remote access: even a local IP connection still needed authentication through Plex, and that authentication depended on Plex's servers being online.
That is why the outage was being searched in real time. By 1:25 PM EDT, Plex had already been down for about an hour, and users were finding that a service built around personal libraries could lock them out of the library sitting in the next room. The status page showed the program guide data for live TV down, along with Discover Together, Movies & Shows free streaming and the plex.tv API.
What made the situation harder to read was the company’s own status reporting. The “what’s down right now” area pointed to several broken services, but the system statuses below it were green basically across the board, leaving a picture of partial failure even while access problems were broad enough to affect local playback.
Plex began as a self-hosted media platform on a local network before expanding into outside-the-network access, and accounts eventually became necessary for anything Plex-related unless local access was set up on the server. That history matters now because the outage hit the part of the service many people assume should keep working even if the wider platform does not.
By 1:25 PM EDT, Plex had sent only one social media message about the outage, and no public explanation had clarified what caused the failure or when full service would be restored. Plex Pass recently went up substantially in price, and some users have already started looking at Jellyfin, which can run completely locally without reaching out to any other servers. For now, the unresolved question is not whether Plex was down; it is how long a media service that depends on distant authentication can stay useful when that authentication disappears.
