User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Gaming
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 1 hr ago. Last stored result reached it in 251 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 233 ms | 0 |
| Mon 21 | 0 | 0.0 | 211 ms | 0 |
| Mon 23 | 0 | 0.0 | 249 ms | 0 |
| Tue 02 | 0 | 0.0 | 242 ms | 0 |
| Tue 04 | 0 | 0.0 | 305 ms | 0 |
| Tue 06 | 0 | 0.0 | 252 ms | 0 |
| Tue 08 | 0 | 0.0 | 234 ms | 0 |
| Tue 10 | 0 | 0.0 | 201 ms | 0 |
| Tue 12 | 0 | 0.0 | 300 ms | 0 |
| Tue 14 | 0 | 0.0 | 245 ms | 0 |
| Tue 17 | 0 | 0.0 | 392 ms | 0 |
| Tue 19 | 0 | 0.0 | 210 ms | 0 |
| Tue 21 | 0 | 0.0 | 338 ms | 0 |
| Tue 23 | 0 | 0.0 | 228 ms | 0 |
| Wed 02 | 0 | 0.0 | 207 ms | 0 |
| Wed 04 | 0 | 0.0 | 205 ms | 0 |
| Wed 06 | 0 | 0.0 | 344 ms | 0 |
| Wed 08 | 0 | 0.0 | 318 ms | 0 |
| Wed 11 | 0 | 0.0 | 217 ms | 0 |
| Wed 13 | 0 | 0.0 | 398 ms | 0 |
| Wed 15 | 0 | 0.0 | 321 ms | 0 |
| Wed 17 | 0 | 0.0 | 255 ms | 0 |
| Wed 19 | 0 | 0.0 | 254 ms | 0 |
| Wed 21 | 0 | 0.0 | 271 ms | 0 |
| Thu 00 | 0 | 0.0 | 367 ms | 0 |
| Thu 02 | 0 | 0.0 | 322 ms | 0 |
| Thu 04 | 0 | 0.0 | 275 ms | 0 |
| Thu 06 | 0 | 0.0 | 216 ms | 0 |
| Thu 08 | 0 | 0.0 | 258 ms | 0 |
| Thu 10 | 0 | 0.0 | 191 ms | 0 |
| Thu 12 | 0 | 0.0 | 192 ms | 0 |
| Thu 14 | 0 | 0.0 | 215 ms | 0 |
| Thu 16 | 0 | 0.0 | 454 ms | 0 |
| Thu 18 | 0 | 0.0 | 272 ms | 0 |
| Thu 20 | 0 | 0.0 | 333 ms | 0 |
| Thu 22 | 0 | 0.0 | 411 ms | 0 |
| Fri 00 | 0 | 0.0 | 285 ms | 0 |
| Fri 02 | 0 | 0.0 | 391 ms | 0 |
| Fri 05 | 0 | 0.0 | 230 ms | 0 |
| Fri 07 | 0 | 0.0 | 168 ms | 0 |
| Fri 09 | 0 | 0.0 | 205 ms | 0 |
| Fri 11 | 0 | 0.0 | 460 ms | 0 |
| Fri 13 | 0 | 0.0 | 398 ms | 0 |
| Fri 15 | 0 | 0.0 | 324 ms | 0 |
| Fri 17 | 0 | 0.0 | 262 ms | 0 |
| Fri 19 | 0 | 0.0 | 418 ms | 0 |
| Fri 20 | 0 | 0.0 | 437 ms | 0 |
| Fri 22 | 0 | 0.0 | 225 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 SpacetimeDB 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 SpacetimeDB goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SpacetimeDB alerts to Slack, Discord or a webhook — free.
SpacetimeDB is listed in our Gaming category and checked at spacetimedb.com. Spacetime (formerly SpacetimeDB) is a reactive backend and real-time database for web apps and games. Write server logic in TypeScript, Rust, C#, or C++, and clients stay in sync automatically.
SpacetimeDB publishes an official status page at status.spacetimedb.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with gaming services: login and matchmaking failures, server disconnects, and store or download errors.
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: 310 ms average, 168–460 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 SpacetimeDB incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
310 ms on average over the last 24 hours (168–460 ms).
Yes, at https://status.spacetimedb.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For gaming services, watch for login and matchmaking failures, server disconnects, and store or download errors. If many people report SpacetimeDB here at once, the problem is on SpacetimeDB'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 SpacetimeDB. 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.