Judoscale had 10 outages in the last 2 years totaling 45h 13m of downtime — averaging 0.4 incidents per month.
There were 10 Judoscale outages since June 10, 2025 totaling 45h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.
Render is reporting API errors, and autoscaling Render apps is temporarily on hold. It will automatically resume once the API is back up and running. We're monitoring their status: https://status.render.com/incidents/xf3skv8xqj3k
The API is responding successfully since the latest Render update. Autoscaling has resumed now.
Fly.io is reporting API errors, and autoscaling Fly apps is temporarily on hold. It will automatically resume once the API is back up and running. We're monitoring their status: https://status.flyio.net/incidents/gvgpvkt454h7
The API is responding successfully and autoscaling has resumed now.
Around 8:40AM UTC we were alerted by an issue reaching both our staging and production apps, and we identified that our current platform (Railway) is having a major outage. We apologize for the disruption, and are monitoring the situation with our platform.
Around 8:40AM UTC we were alerted by an issue reaching both our staging and production apps, and we identified that our current platform (Railway) was having a major outage. It seemed to recover in ~20 min, but during that time both web and ingest were hitting "502 Bad Gateway" or Cloudflare errors trying to reach the app. We apologize for the disruption, and are monitoring the situation with our platform.
Web and ingest traffic have normalized.
We're looking into some errors contacting our Redis instances, and the app is down.
App & autoscaling are up and running.
Autoscaling is currently failing for Heroku apps. We are investigating the issue and will update soon.
Autoscaling is up and running.
We're seeing an increase in errors from Heroku when trying to talk to their API and trigger autoscaling, started around 12:05 UTC.
The incident has been closed on the Heroku status page, and autoscaling is up and running.
Judoscale is currently unavailable via web and our autoscaler is not operational. We are investigating.
Looks like Heroku's API started working just as I was posting the last update. Everything looking good as of now... Continuing to monitor.
We've received some reports of upscaling not triggering, and are investigating.
Upscaling is working as expected. We'll be writing up a full report of what happened and what we're doing about it, but here's a summary: At 2025-08-07 00:25:00 UTC we ingested some unexpected queue metrics for a far-future date. It looks like a customer triggered this from their laptop. Our upscale logic looks at the most recent metrics bucket as a boundary, so this data broke our upscaling. We have many automated checks in place, but none caught this, and unfortunately it happened overnight for us, so we weren't aware of the issue until this morning around 2025-08-07 12:00:00 UTC. We identified the bad data and deleted it at 2025-08-07 12:36:00 UTC. Upscaling immediately started working as expected. We're implementing a permanent fix now, as well as automated checks so that we're alerted immediately in the future. Check our blog later today for a more thorough write-up.
We're currently unable to scale Render apps due to an API outage: https://status.render.com/incidents/mmx0fcpls23x
Render API is back up.
We're currently unable to scale Heroku apps due to an API outage. Heroku has created an incident on their status page at https://status.heroku.com/incidents/2822, but their status page is failing to load sometimes.
Heroku reports that everything is operating normally.