User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 335 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 383 ms | 0 |
| Mon 17 | 0 | 0.0 | 481 ms | 0 |
| Mon 19 | 0 | 0.0 | 227 ms | 0 |
| Mon 21 | 0 | 0.0 | 163 ms | 0 |
| Mon 23 | 0 | 0.0 | 217 ms | 0 |
| Tue 02 | 0 | 0.0 | 260 ms | 0 |
| Tue 04 | 0 | 0.0 | 519 ms | 0 |
| Tue 06 | 0 | 0.0 | 207 ms | 0 |
| Tue 08 | 0 | 0.0 | 262 ms | 0 |
| Tue 10 | 0 | 0.0 | 353 ms | 0 |
| Tue 12 | 0 | 0.0 | 421 ms | 0 |
| Tue 14 | 0 | 0.0 | 305 ms | 0 |
| Tue 17 | 0 | 0.0 | 473 ms | 0 |
| Tue 19 | 0 | 0.0 | 445 ms | 0 |
| Tue 21 | 0 | 0.0 | 444 ms | 0 |
| Tue 23 | 0 | 0.0 | 499 ms | 0 |
| Wed 02 | 0 | 0.0 | 294 ms | 0 |
| Wed 04 | 0 | 0.0 | 362 ms | 0 |
| Wed 06 | 0 | 0.0 | 384 ms | 0 |
| Wed 08 | 0 | 0.0 | 255 ms | 0 |
| Wed 11 | 0 | 0.0 | 460 ms | 0 |
| Wed 13 | 0 | 0.0 | 507 ms | 0 |
| Wed 15 | 0 | 0.0 | 231 ms | 0 |
| Wed 17 | 0 | 0.0 | 493 ms | 0 |
| Wed 19 | 0 | 0.0 | 519 ms | 0 |
| Wed 21 | 0 | 0.0 | 436 ms | 0 |
| Wed 23 | 0 | 0.0 | 282 ms | 0 |
| Thu 02 | 0 | 0.0 | 197 ms | 0 |
| Thu 04 | 0 | 0.0 | 345 ms | 0 |
| Thu 05 | 0 | 0.0 | 261 ms | 0 |
| Thu 07 | 0 | 0.0 | 298 ms | 0 |
| Thu 09 | 0 | 0.0 | 396 ms | 0 |
| Thu 11 | 0 | 0.0 | 223 ms | 0 |
| Thu 13 | 0 | 0.0 | 260 ms | 0 |
| Thu 15 | 0 | 0.0 | 443 ms | 0 |
| Thu 17 | 0 | 0.0 | 451 ms | 0 |
| Thu 19 | 0 | 0.0 | 393 ms | 0 |
| Thu 21 | 0 | 0.0 | 433 ms | 0 |
| Thu 23 | 0 | 0.0 | 237 ms | 0 |
| Fri 01 | 0 | 0.0 | 169 ms | 0 |
| Fri 03 | 0 | 0.0 | 486 ms | 0 |
| Fri 05 | 0 | 0.0 | 503 ms | 0 |
| Fri 08 | 0 | 0.0 | 270 ms | 0 |
| Fri 09 | 0 | 0.0 | 319 ms | 0 |
| Fri 11 | 0 | 0.0 | 409 ms | 0 |
| Fri 12 | 0 | 0.0 | 310 ms | 0 |
| Fri 14 | 0 | 0.0 | 317 ms | 0 |
| Fri 16 | 0 | 0.0 | 335 ms | 0 |
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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for DBOS yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when DBOS goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send DBOS alerts to Slack, Discord or a webhook — free.
We track DBOS (dbos.dev) as part of the Cloud & developer group. DBOS is an open source durable execution and workflow orchestration system that simplifies building and operating reliable, observable workflows.
DBOS publishes an official status page at status.dbos.dev; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 340 ms average, 28–503 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public DBOS incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
340 ms on average over the last 24 hours (28–503 ms).
Yes, at https://status.dbos.dev.
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 DBOS here at once, the problem is on DBOS'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 DBOS. 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.