Today I’m back to having Up next to watch never load.
Timeouting again, getting Cloudlfare errors, like 524 and 521.
not as often as before but yes still - me too: 521 errors
I’m having issues at random too. Same errors, 521 mostly.
1 Like
I am getting a 521 error as well, a lot of start and stop.
Edit: Now it is working for me again.
Same issue here for several days.
I’ve also been having frequent time-out errors, too.
1 Like
Yeah I’ve been having this issue for a few days too.
1 Like
Same here. Consistent error 521 host down messages. Been happening for at least a month. All devices.
2 Likes
It’s worse than ever this morning - getting 521 errors more than it working. Additionally the add to watchlist button only shows watchlist, not my personal lists as options. And when I add to watchlist it doesn’t actually add. It’s starting to feel like a lot of things are just falling apart.
It’s getting worse. There is no evening (GMT+2) when I can just watch a show and check-in. I have to retry every few minutes until it finally works.
It’s hit and miss for me too… definitely a CDN issue.
I think you might need to chat with the DNS and CACHE hosting company.
You might need to upgrade to their next tier of server?
Is that possible?
Paully
We’re sorry for all the recent performance issues. There are a series of different things going on causing the issues. It seems like we fix one thing, then another issue pops up. The most recent issue was 1 web server ran out of disk space and was the cause of the 521 errors. It was inconsistent since most of the web servers were working fine, but that 1 server had issues which was causing issues. We’re working on an automated way to handle the disk issues to hopefully avoid that in the future.
As Sean mentioned earlier, there are some ongoing issues with rogue API apps that causing some database performance issues. We’ll be implementing more strict API limits to deal with that and the plan is to roll those out this week.
7 Likes
This is really sad, every unrestricted API will be abused at some point.
Thanks for checking and hopefully fixing.
A few days ago we pushed some server updates specifically related to the 521 errors. Over this weekend, please let us know if you see 521 errors still. If so, please include the specific time, url, and if you are seeing more or less of the errors compared to several weeks ago. Thanks.
1 Like
My friend, who is not a VIP, has been having problems with 521 errors today. (not only today though, but still today after your message).
And when she does get in, nothing loads, like so:
Then when she refreshes, she gets 521 again 
She managed to make it work long enough to log an episode of Drag Race Holland (she’s not Dutch though!).
I just got an error myself. 22:40 GMT+1. my timezone. Refreshing works for me though.
22:44
I get that usually between 8 and 11 pm in GMT+1 zone. I’m using the SeriesGuide app on Android to check-in what I’m watching.
Beta App is extremely slow / not responding for days at different times now. Right now (10:01pm cest), but also morning, mid-day, evenings for about a week now.
While I’m seeing less of the timeouts and saw none this weekend. Up next to watch still almost never loads, haven’t got it to load at all yesterday or today. And the upcoming schedule section often requires multiple refreshes to load.
1 Like
@lifeiscrazy hmm, my guess is all those dashboard sections are getting errors. We’d need to look at your friends account directly, so if they can email support@trakt.tv with the details that would be great. There might be something else going on.
@mithrial are you getting errors in SeriesGuide or the Trakt website?
@Parzival which specific sections aren’t loading in the app? I wonder if it’s related to API limits. We can take this discussion into a separate http://forums.trakt.tv/c/trakt/iphone-beta if that makes sense too.
@polargeek I’m testing this out right now. It appears the large number of unique show’s you’ve watched is causing the timeout issues.
1 Like