User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
dbdiagram.io · 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 43 min ago. Last stored result reached it in 288 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 683 ms | 0 |
| Tue 01 | 0 | 0.0 | 306 ms | 0 |
| Tue 03 | 0 | 0.0 | 309 ms | 0 |
| Tue 05 | 0 | 0.0 | 299 ms | 0 |
| Tue 07 | 0 | 0.0 | 324 ms | 0 |
| Tue 09 | 0 | 0.0 | 279 ms | 0 |
| Tue 11 | 0 | 0.0 | 279 ms | 0 |
| Tue 13 | 0 | 0.0 | 635 ms | 0 |
| Tue 16 | 0 | 0.0 | 804 ms | 0 |
| Tue 18 | 0 | 0.0 | 716 ms | 0 |
| Tue 20 | 0 | 0.0 | 744 ms | 0 |
| Tue 22 | 0 | 0.0 | 523 ms | 0 |
| Wed 01 | 0 | 0.0 | 720 ms | 0 |
| Wed 03 | 0 | 0.0 | 719 ms | 0 |
| Wed 05 | 0 | 0.0 | 770 ms | 0 |
| Wed 07 | 0 | 0.0 | 320 ms | 0 |
| Wed 10 | 0 | 0.0 | 293 ms | 0 |
| Wed 12 | 0 | 0.0 | 665 ms | 0 |
| Wed 14 | 0 | 0.0 | 611 ms | 0 |
| Wed 16 | 0 | 0.0 | 318 ms | 0 |
| Wed 18 | 0 | 0.0 | 397 ms | 0 |
| Wed 20 | 0 | 0.0 | 773 ms | 0 |
| Wed 23 | 0 | 0.0 | 688 ms | 0 |
| Thu 01 | 0 | 0.0 | 490 ms | 0 |
| Thu 03 | 0 | 0.0 | 371 ms | 0 |
| Thu 05 | 0 | 0.0 | 302 ms | 0 |
| Thu 07 | 0 | 0.0 | 353 ms | 0 |
| Thu 09 | 0 | 0.0 | 790 ms | 0 |
| Thu 11 | 0 | 0.0 | 272 ms | 0 |
| Thu 13 | 0 | 0.0 | 767 ms | 0 |
| Thu 15 | 0 | 0.0 | 311 ms | 0 |
| Thu 17 | 0 | 0.0 | 786 ms | 0 |
| Thu 19 | 0 | 0.0 | 303 ms | 0 |
| Thu 21 | 0 | 0.0 | 313 ms | 0 |
| Thu 23 | 0 | 0.0 | 300 ms | 0 |
| Fri 01 | 0 | 0.0 | 360 ms | 0 |
| Fri 03 | 0 | 0.0 | 421 ms | 0 |
| Fri 06 | 0 | 0.0 | 756 ms | 0 |
| Fri 08 | 0 | 0.0 | — | 0 |
| Fri 10 | 0 | 0.0 | 496 ms | 0 |
| Fri 11 | 0 | 0.0 | 610 ms | 0 |
| Fri 13 | 0 | 0.0 | 764 ms | 0 |
| Fri 15 | 0 | 0.0 | 275 ms | 0 |
| Fri 17 | 0 | 0.0 | — | 0 |
| Fri 18 | 0 | 0.0 | 659 ms | 0 |
| Fri 20 | 0 | 0.0 | 354 ms | 0 |
| Fri 21 | 0 | 0.0 | 351 ms | 0 |
| Fri 23 | 0 | 0.0 | 288 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 dbdiagram 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 dbdiagram goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send dbdiagram alerts to Slack, Discord or a webhook — free.
dbdiagram is listed in our Cloud & developer category and checked at dbdiagram.io. Draw database relationship diagrams in seconds by writing simple DBML code. Free, fast, and built for developers and data analysts.
dbdiagram publishes an official status page at status.dbdiagram.io; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 486 ms average, 275–764 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public dbdiagram incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
486 ms on average over the last 24 hours (275–764 ms).
Yes, at https://status.dbdiagram.io.
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 dbdiagram here at once, the problem is on dbdiagram'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 dbdiagram. 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.