User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Runable 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 → runable.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 41 min ago. Last stored result reached it in 126 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 |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 852 ms | 0 |
| Nov 7 | 0 | 0.0 | 88 ms | 0 |
| Nov 7 | 0 | 0.0 | 1000 ms | 0 |
| Nov 7 | 0 | 0.0 | 1107 ms | 0 |
| Nov 8 | 0 | 0.0 | 924 ms | 0 |
| Nov 8 | 0 | 0.0 | 988 ms | 0 |
| Nov 8 | 0 | 0.0 | 98 ms | 0 |
| Nov 8 | 0 | 0.0 | 1085 ms | 0 |
| Nov 9 | 0 | 0.0 | 1068 ms | 0 |
| Nov 9 | 0 | 0.0 | 886 ms | 0 |
| Nov 9 | 0 | 0.0 | 1101 ms | 0 |
| Nov 9 | 0 | 0.0 | 1333 ms | 0 |
| Nov 10 | 0 | 0.0 | 1260 ms | 0 |
| Nov 10 | 0 | 0.0 | 769 ms | 0 |
| Nov 10 | 0 | 0.0 | 1021 ms | 0 |
| Nov 10 | 0 | 0.0 | 1017 ms | 0 |
| Nov 11 | 0 | 0.0 | 1124 ms | 0 |
| Nov 11 | 0 | 0.0 | 1229 ms | 0 |
| Nov 11 | 0 | 0.0 | 494 ms | 0 |
| Nov 11 | 0 | 0.0 | 797 ms | 0 |
| Nov 12 | 0 | 0.0 | 901 ms | 0 |
| Nov 12 | 0 | 0.0 | 237 ms | 0 |
| Nov 12 | 0 | 0.0 | 1324 ms | 0 |
| Nov 12 | 0 | 0.0 | 127 ms | 0 |
| Nov 13 | 0 | 0.0 | 1372 ms | 0 |
| Nov 13 | 0 | 0.0 | 588 ms | 0 |
| Nov 13 | 0 | 0.0 | 126 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Runable 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 Runable yet. Outages of 10 minutes or more get their own page here.
Having trouble with Runable?
One report per service every 10 minutes from this network. No account.
Follow Runable
Get an email when Runable goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Runable alerts to Slack, Discord or a webhook — free.
About Runable
We track Runable (runable.com) as part of the AI group. Runable is the AI general agent that thinks, plans, and executes end-to-end, so you can Build, Run & Grow.
Runable publishes an official status page at status.runable.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 707 ms average, 69–1753 ms range across 12 successful checks.
Questions
Is Runable down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Runable last down?
We have not recorded a public Runable incident since monitoring began 8 days ago.
What is Runable's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Runable respond?
707 ms on average over the last 24 hours (69–1753 ms).
Does Runable have an official status page?
Yes, at https://status.runable.com.
Runable 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 AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Runable here at once, the problem is on Runable'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 Runable. 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.