Skip to main content

Is Trakt Down?

No — Trakt is up
Trakt's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 226 ms

Right now

The verdict is the worse of these two. How we decide

Trakt's status page

status.trakt.tv · read · checked every 3 minutes

Operational
Trakt's components, as its status page reports them
ComponentStatus
HistoryOperational
TrendingOperational
Web AppOperational
Open their status page

FlareWarden checks

trakt.tv from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
226 ms
Checked

By region

  • Amsterdam reachable, 222 ms
  • Chicago reachable, 212 ms
  • Paris reachable, 254 ms
  • San Jose reachable, 271 ms
  • Singapore reachable, 366 ms
  • Stockholm reachable, 103 ms
  • Sydney reachable, 108 ms
  • Toronto reachable, 275 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam10 ms3 ms9 ms216 ms
Chicago23 ms1 ms8 ms209 ms
Paris21 ms2 ms10 ms251 ms
San Jose19 ms2 ms11 ms265 ms
Singapore10 ms2 ms8 ms362 ms
Stockholm13 ms2 ms9 ms99 ms
Sydney15 ms1 ms9 ms106 ms
Toronto65 ms1 ms10 ms272 ms
We check that trakt.tv loads, not every feature behind it. Test it yourself

History

Incidents Trakt reported

Since Oct 27, 10 days · from status.trakt.tv

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

Trakt website availability

Measured by FlareWarden · trakt.tv

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

Last 30 days

91-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 29 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of trakt.tv from multiple regions every 6 hours. Trakt's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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

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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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 the verdict is the worse of what it reports and what our checks see: a major outage of Trakt itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Trakt goes down

We check Trakt every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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