User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
surrealdb.com · 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 1624 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 522 ms | 0 |
| Nov 7 | 0 | 0.0 | 530 ms | 0 |
| Nov 7 | 0 | 0.0 | 486 ms | 0 |
| Nov 7 | 0 | 0.0 | 468 ms | 0 |
| Nov 7 | 0 | 0.0 | 421 ms | 0 |
| Nov 8 | 0 | 0.0 | 473 ms | 0 |
| Nov 8 | 0 | 0.0 | 473 ms | 0 |
| Nov 8 | 0 | 0.0 | 514 ms | 0 |
| Nov 8 | 0 | 0.0 | 436 ms | 0 |
| Nov 9 | 0 | 0.0 | 429 ms | 0 |
| Nov 9 | 0 | 0.0 | 468 ms | 0 |
| Nov 9 | 0 | 0.0 | 574 ms | 0 |
| Nov 9 | 0 | 0.0 | 1730 ms | 0 |
| Nov 10 | 0 | 0.0 | 1101 ms | 0 |
| Nov 10 | 0 | 0.0 | 836 ms | 0 |
| Nov 10 | 0 | 0.0 | 657 ms | 0 |
| Nov 10 | 0 | 0.0 | 83 ms | 0 |
| Nov 11 | 0 | 0.0 | 1404 ms | 0 |
| Nov 11 | 0 | 0.0 | 759 ms | 0 |
| Nov 11 | 0 | 0.0 | 1045 ms | 0 |
| Nov 11 | 0 | 0.0 | 992 ms | 0 |
| Nov 12 | 0 | 0.0 | 1107 ms | 0 |
| Nov 12 | 0 | 0.0 | 904 ms | 0 |
| Nov 12 | 0 | 0.0 | 744 ms | 0 |
| Nov 12 | 0 | 0.0 | 1356 ms | 0 |
| Nov 13 | 0 | 0.0 | 241 ms | 0 |
| Nov 13 | 0 | 0.0 | 754 ms | 0 |
| Nov 13 | 0 | 0.0 | 1315 ms | 0 |
| Nov 13 | 0 | 0.0 | 1889 ms | 0 |
| Nov 14 | 0 | 0.0 | 835 ms | 0 |
| Nov 14 | 0 | 0.0 | 1013 ms | 0 |
| Nov 14 | 0 | 0.0 | 1697 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for SurrealDB 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 SurrealDB goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SurrealDB alerts to Slack, Discord or a webhook — free.
We track SurrealDB (surrealdb.com) as part of the Cloud & developer group. SurrealDB is the database and memory for every agent: it starts on its first query, scales to zero, speaks Postgres and MySQL, and remembers in one query.
SurrealDB publishes an official status page at status.surrealdb.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: 1404 ms average, 110–2860 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public SurrealDB incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
1404 ms on average over the last 24 hours (110–2860 ms).
Yes, at https://status.surrealdb.com.
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 SurrealDB here at once, the problem is on SurrealDB'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 SurrealDB. 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.