Skip to main content

Is Trakt Down?

No — Trakt is up

Reachable from all 8 checked regions

Average response time: 253ms

Last checked · checks run every 6 hours

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

Components the vendor reports as affected: History Down Scrobbling Down Checkin Down

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical.

Trakt uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
223ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 16 checks
Jun 29 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
275ms
DNS 19ms TCP 7ms TLS 12ms TTFB 238ms
arn
191ms
DNS 17ms TCP 1ms TLS 7ms TTFB 186ms
bom
387ms
DNS 40ms TCP 2ms TLS 10ms TTFB 377ms
cdg
213ms
DNS 15ms TCP 5ms TLS 12ms TTFB 203ms
ord
129ms
DNS 10ms TCP 2ms TLS 10ms TTFB 124ms
sin
332ms
DNS 10ms TCP 0ms TLS 6ms TTFB 327ms
sjc
224ms
DNS 69ms TCP 0ms TLS 6ms TTFB 219ms
syd
298ms
DNS 7ms TCP 0ms TLS 7ms TTFB 294ms
yyz
107ms
DNS 7ms TCP 0ms TLS 8ms TTFB 101ms

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 all 18 regions to find out where it breaks.

Test it yourself

Related services

P
Plex
I
IMDb
V
Vimeo
S
SoundCloud

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 — 8 of them answered the most recent check.
  • 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, and let it override us in both directions.

Get alerted when Trakt goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required