There still seem to be issues. During the night, no cloud backup could be created on my end due to a timeout. Manually it doesn’t work either, and now it says that I’ve reached the maximum number of updates per 24 hours, even though none were successful.
Same Problem concerning the backup.
No (online) backups here either. Updating apps from the App Store is also very inconsistent. It keeps asking for credentials until it finally succeeds.
Since the incident, degraded services, from yesterday (24-01) are registered as resolved, I think it’s a good idea to lock this topic and create a new topic for the current backup issue. @Dijker
I would keep this current topic open, as it all seems to be related to the big outage yesterday. And there seem to be more issues than just backups…
Well, seems is the keyword here. Athom states the problem was resolved, so refering back to it may lead to researching in the wrong direction.
When treating this as a new issue it’s most likely to get proper attention and folowup. When Athom finds out it was related, that’s nice for them to know and useful for updating their procedures, but that’s for after the show.
But then again, that’s just my opinion on how to handle service disruptions.
I got the same thing.
its unstable. i had a strange error with mfa.
Here also no automatic backup last night, When going to settings and backup, there is an error.
So not solved yet…
I’ve also got backup errors: it says I have no backups, and then times out when I try to create one manually.
Also, I couldn’t run voice commands via Google last night, and while they’re working this morning, the latency is horrible.
But Athom “doesn’t read along here”… 
As it’s not just backups, but more problems still (that also existed yesterday with the outage; it is a very fair assumption that it is related imho…
I created a support ticket for these issues: Backup issues - #9 by SunBeech
1 Like
It’s not just backups. The developer tools also doesn’t work. You have to refresh multiple times, because the /delegation/token request to api.athom.com sometimes returns status code 503 or simply times out
When I publish new versions of my apps, it also says “Timeout after 10000ms” and I have to try again 2 or 3 times to publish the new versions
1 Like
It all seems related to api.athom.com, their auth API. Sometimes, the avatars in the web app don’t load correctly. After checking the Network tab of Chrome DevTools, I see that the request to api.athom.com timed out
Ah yes, I noted that also yesterday. Nice that you were able to track down the source of the various issues 
. I assume also Athom employees must be aware, as many use Homey themselves.
I have also been getting from user/me an empty collection for my two homeys. Have you seen the same behaviour?
My nightly, planned backup was successful again tonight…
