[Incident] Service degraded - Integrations and API - 20260124T10h30 CET - Was: Homey Cloud is down

I see the webhooks.athom.com returns

Operation `webhooks.findOne()` buffering timed out after 10000ms

When triggering a webhook. So that still doesn’t work.

1 Like

Yes, that also uses webhooks.athom.com. I think the login issue is related to the callback.athom.com service, which is used for OAuth2 callback URLs.

I guess…

Now it doesn’t load the apps anymore either. It did work for a while (I was able to publish a new version of one of my apps 30 minutes ago), but now it doesn’t load anymore.

It seems to be unstable, since now it loads again after a few refreshes. It seems like services are slowly restoring.

I think IFTTT not working neither.

Webhooks just restarted…

Yes, Webhooks are also working again here.

Managed to restart whitings app too…

Again ??

It still works here. But the developer tools sometimes doesn’t work (I have to submit my app builds multiple times for it to work)

I have trouble with Google Assistent. Sometimes it works but sometimes it gives timeout errors.

1 Like

Not sure whether related to the cloud connection issues of today, but when I check for updates in the mobile app I get this error:

Also Siri Shortcuts don’t work anymore.

That appears to be a DB issue. Also, I think that error message comes from the Homey server, not from Homey itself.

That mongodb.net domain resolves to a local IP address, so I think the issue is in their datacenter. Not sure if Homey can fix it though, as it seems to be related to MongoDB Atlas or AWS.

1 Like

I also see other users in Homey groups on Facebook reporting the same error, so I assume it is something on Athom’s side (or one of the services provided by the third parties they use).

The issue still hasn’t been resolved

When checking the Network tab in DevTools, I see this. This doesn’t happen everytime (I have to refresh a few times to view my apps and publish new versions)

This is the server response:

{"code":503,"error":"server_error","error_description":"server_error"}

Same when publishing new versions from the CLI. I have to retry a few times

Also got this when triggering a webhook.homey.app webhook:

Error: Timeout after 10000ms
    at Util.timeout (/node_modules/homey-api/lib/Util.js:57:26)
    at AthomCloudAPI.onCallRequestExecute (/node_modules/homey-api/lib/API.js:225:17)
    at AthomCloudAPI.call (/node_modules/homey-api/lib/API.js:166:31)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Server.determineRoute (/app/src/lib/Server.js:69:31)
    at async Object.getTarget (/node_modules/http-proxy-middleware/dist/router.js:14:21)
    at async HttpProxyMiddleware.applyRouter (/node_modules/http-proxy-middleware/dist/http-proxy-middleware.js:110:29)
    at async HttpProxyMiddleware.prepareProxyRequest (/node_modules/http-proxy-middleware/dist/http-proxy-middleware.js:97:13)
    at async HttpProxyMiddleware.middleware (/node_modules/http-proxy-middleware/dist/http-proxy-middleware.js:21:48)

The second time it worked fine. So it seems partially resolved, but definitely not fully. It’s pretty unstable

The error was sent by the server, not by Homey itself.