User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
judoscale.com · Cloud & developer
Is Judoscale down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → judoscale.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 138 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 04 | 0 | 0.0 | 369 ms | 0 |
| Tue 06 | 0 | 0.0 | 287 ms | 0 |
| Tue 08 | 0 | 0.0 | 209 ms | 0 |
| Tue 10 | 0 | 0.0 | 243 ms | 0 |
| Tue 12 | 0 | 0.0 | 126 ms | 0 |
| Tue 14 | 0 | 0.0 | 168 ms | 0 |
| Tue 17 | 0 | 0.0 | 152 ms | 0 |
| Tue 19 | 0 | 0.0 | 252 ms | 0 |
| Tue 21 | 0 | 0.0 | 248 ms | 0 |
| Tue 23 | 0 | 0.0 | 338 ms | 0 |
| Wed 01 | 0 | 0.0 | 145 ms | 0 |
| Wed 04 | 0 | 0.0 | 267 ms | 0 |
| Wed 06 | 0 | 0.0 | 325 ms | 0 |
| Wed 08 | 0 | 0.0 | 339 ms | 0 |
| Wed 11 | 0 | 0.0 | 300 ms | 0 |
| Wed 13 | 0 | 0.0 | 333 ms | 0 |
| Wed 15 | 0 | 0.0 | 323 ms | 0 |
| Wed 17 | 0 | 0.0 | 361 ms | 0 |
| Wed 19 | 0 | 0.0 | 339 ms | 0 |
| Wed 21 | 0 | 0.0 | 314 ms | 0 |
| Wed 23 | 0 | 0.0 | 278 ms | 0 |
| Thu 02 | 0 | 0.0 | 400 ms | 0 |
| Thu 04 | 0 | 0.0 | 213 ms | 0 |
| Thu 06 | 0 | 0.0 | 139 ms | 0 |
| Thu 08 | 0 | 0.0 | 159 ms | 0 |
| Thu 10 | 0 | 0.0 | 259 ms | 0 |
| Thu 12 | 0 | 0.0 | 140 ms | 0 |
| Thu 14 | 0 | 0.0 | 181 ms | 0 |
| Thu 16 | 0 | 0.0 | 322 ms | 0 |
| Thu 18 | 0 | 0.0 | 193 ms | 0 |
| Thu 20 | 0 | 0.0 | 230 ms | 0 |
| Thu 22 | 0 | 0.0 | 183 ms | 0 |
| Fri 00 | 0 | 0.0 | 289 ms | 0 |
| Fri 02 | 0 | 0.0 | 246 ms | 0 |
| Fri 04 | 0 | 0.0 | 231 ms | 0 |
| Fri 06 | 0 | 0.0 | 286 ms | 0 |
| Fri 09 | 0 | 0.0 | 160 ms | 0 |
| Fri 10 | 0 | 0.0 | 289 ms | 0 |
| Fri 11 | 0 | 0.0 | 261 ms | 0 |
| Fri 13 | 0 | 0.0 | 277 ms | 0 |
| Fri 15 | 0 | 0.0 | 307 ms | 0 |
| Fri 17 | 0 | 0.0 | 306 ms | 0 |
| Fri 19 | 0 | 0.0 | 392 ms | 0 |
| Fri 20 | 0 | 0.0 | 317 ms | 0 |
| Fri 22 | 0 | 0.0 | 288 ms | 0 |
| Sat 00 | 0 | 0.0 | 321 ms | 0 |
| Sat 02 | 0 | 0.0 | 155 ms | 0 |
| Sat 05 | 0 | 0.0 | 218 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Judoscale badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Judoscale yet. Outages of 10 minutes or more get their own page here.
Having trouble with Judoscale?
One report per service every 10 minutes from this network. No account.
Follow Judoscale
Get an email when Judoscale goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Judoscale alerts to Slack, Discord or a webhook — free.
About Judoscale
Judoscale, at judoscale.com, is one of the Cloud & developer services we monitor. A more powerful autoscaler for Heroku, Render, Railway, Fly.io, Scalingo, Northflank, and Amazon ECS. Queue-time scaling for web and workers, with per-process ranges, step size, and schedules.
Judoscale publishes an official status page at status.judoscale.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 274 ms average, 138–392 ms range across 16 successful checks.
Questions
Is Judoscale down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Judoscale last down?
We have not recorded a public Judoscale incident since monitoring began 9 days ago.
What is Judoscale's uptime?
From our own checks: 100% over 9 days of checks.
How fast does Judoscale respond?
274 ms on average over the last 24 hours (138–392 ms).
Does Judoscale have an official status page?
Yes, at https://status.judoscale.com.
Judoscale not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Judoscale here at once, the problem is on Judoscale's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Judoscale. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.