Is Trakt Down?

No — Trakt is up

Reachable from all 8 checked regions

Average response time: 254ms

Last checked 2 hours ago · checks run every 6 hours

Official status page: https://status.trakt.tv

Trakt uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

290ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 76 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

76-day clean streak

Sep 12 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

269ms

DNS 19ms TCP 1ms TLS 8ms TTFB 266ms

arn

693ms

DNS 322ms TCP 1ms TLS 7ms TTFB 691ms

cdg

226ms

DNS 26ms TCP 2ms TLS 7ms TTFB 223ms

dfw

178ms

DNS 14ms TCP 2ms TLS 10ms TTFB 172ms

ewr

127ms

DNS 17ms TCP 2ms TLS 12ms TTFB 121ms

sjc

238ms

DNS 12ms TCP 2ms TLS 9ms TTFB 235ms

syd

118ms

DNS 12ms TCP 1ms TLS 8ms TTFB 116ms

yyz

185ms

DNS 9ms TCP 1ms TLS 11ms TTFB 182ms

What Trakt does

Trakt records what people watch, syncing automatically from media servers and apps to build a viewing history, watchlists and progress through series. Most of its use is invisible: other applications scrobble to it in the background, so an outage is usually noticed as a media player complaining rather than through the website.

What an outage looks like

Scrobbles from Plex, Kodi and similar applications fail, so watched episodes do not register and progress stalls mid-series. Third-party apps built on the Trakt API show empty watchlists or fail to sign in. The website loads slowly or not at all. Lists and calendars appear stale, and syncing a device set up during the incident does not complete.

What to do about it

Check status.trakt.tv, which reports overall uptime rather than splitting the service into many components. Most scrobbling clients queue failed items and retry, so watched episodes usually appear once the service returns. Avoid manually marking a long run of episodes as watched during an outage, since the queued scrobbles then arrive and duplicate them.

Is it down for everyone, or just you?

If this page says Trakt is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Trakt outage FAQ

Will my watched episodes sync after a Trakt outage?

Usually. Most scrobbling clients, including Plex and Kodi plugins, queue items that failed to send and retry later, so history fills in once the service recovers. Marking those episodes manually in the meantime is the main cause of duplicate entries, because the queued scrobbles arrive afterwards and are recorded again.

Is Trakt down or has my API token expired?

Tokens expire and produce an authorisation error in the client rather than a timeout, and reconnecting the application fixes it. An outage affects every client at once. Check status.trakt.tv, then whether other Trakt-connected apps are also failing. If only one application is complaining, reauthorise that one rather than waiting.

Does a Trakt outage stop my media server working?

No. Plex, Jellyfin and similar servers play media independently and only report to Trakt afterwards. Playback continues normally throughout; what fails is the record of it. The scrobbling plugin may log errors, which looks alarming in the server log but has no effect on your ability to watch anything.

Why do third-party apps show an empty watchlist?

Many applications read watchlists live from the Trakt API rather than caching them, so an incident leaves them showing nothing rather than an error. That reads as a deleted list, which is understandably alarming. The data is intact on Trakt's side and reappears once the API recovers; no restoration is needed.

Should I re-scan my library during a Trakt outage?

No. A full re-scan generates a large volume of sync activity that will fail during the incident and then flood the service during recovery, which can produce duplicates and slow your own catch-up. Wait until the status page is clear, then let normal scrobbling resume rather than forcing a rebuild.

How we measure this

We request Trakt's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Trakt publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Trakt goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required