User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 20 min ago. Last stored result reached it in 290 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 250 ms | 0 |
| Mon 19 | 0 | 0.0 | 290 ms | 0 |
| Mon 22 | 0 | 0.0 | 280 ms | 0 |
| Tue 00 | 0 | 0.0 | 165 ms | 0 |
| Tue 02 | 0 | 0.0 | 226 ms | 0 |
| Tue 04 | 0 | 0.0 | 405 ms | 0 |
| Tue 06 | 0 | 0.0 | 279 ms | 0 |
| Tue 08 | 0 | 0.0 | 92 ms | 0 |
| Tue 10 | 0 | 0.0 | 534 ms | 0 |
| Tue 12 | 0 | 0.0 | 96 ms | 0 |
| Tue 15 | 0 | 0.0 | 158 ms | 0 |
| Tue 17 | 0 | 0.0 | 121 ms | 0 |
| Tue 19 | 0 | 0.0 | 233 ms | 0 |
| Tue 21 | 0 | 0.0 | 206 ms | 0 |
| Wed 00 | 0 | 0.0 | 264 ms | 0 |
| Wed 02 | 0 | 0.0 | 368 ms | 0 |
| Wed 04 | 0 | 0.0 | 494 ms | 0 |
| Wed 06 | 0 | 0.0 | 446 ms | 0 |
| Wed 09 | 0 | 0.0 | 552 ms | 0 |
| Wed 11 | 0 | 0.0 | 364 ms | 0 |
| Wed 13 | 0 | 0.0 | 450 ms | 0 |
| Wed 15 | 0 | 0.0 | 227 ms | 0 |
| Wed 17 | 0 | 0.0 | 219 ms | 0 |
| Wed 19 | 0 | 0.0 | 155 ms | 0 |
| Wed 22 | 0 | 0.0 | 136 ms | 0 |
| Thu 00 | 0 | 0.0 | 431 ms | 0 |
| Thu 02 | 0 | 0.0 | 378 ms | 0 |
| Thu 04 | 0 | 0.0 | 179 ms | 0 |
| Thu 06 | 0 | 0.0 | 436 ms | 0 |
| Thu 08 | 0 | 0.0 | 107 ms | 0 |
| Thu 10 | 0 | 0.0 | 116 ms | 0 |
| Thu 12 | 0 | 0.0 | 239 ms | 0 |
| Thu 14 | 0 | 0.0 | 94 ms | 0 |
| Thu 16 | 0 | 0.0 | 187 ms | 0 |
| Thu 18 | 0 | 0.0 | 132 ms | 0 |
| Thu 20 | 0 | 0.0 | 200 ms | 0 |
| Thu 22 | 0 | 0.0 | 147 ms | 0 |
| Fri 00 | 0 | 0.0 | 77 ms | 0 |
| Fri 02 | 0 | 0.0 | 125 ms | 0 |
| Fri 05 | 0 | 0.0 | 259 ms | 0 |
| Fri 07 | 0 | 0.0 | 92 ms | 0 |
| Fri 09 | 0 | 0.0 | 253 ms | 0 |
| Fri 10 | 0 | 0.0 | 716 ms | 0 |
| Fri 11 | 0 | 0.0 | 757 ms | 0 |
| Fri 14 | 0 | 0.0 | 425 ms | 0 |
| Fri 15 | 0 | 0.0 | 410 ms | 0 |
| Fri 17 | 0 | 0.0 | 290 ms | 0 |
| Fri 19 | 0 | 0.0 | 126 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Decart 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 Decart goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Decart alerts to Slack, Discord or a webhook — free.
Decart, at decart.ai, is one of the AI services we monitor. Decart is a frontier AI lab building real-time world models - environments that respond instantly and run at millisecond latency with unprecedented efficiency.
Decart publishes an official status page at status.decart.ai; 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: 280 ms average, 54–757 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Decart incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
280 ms on average over the last 24 hours (54–757 ms).
Yes, at https://status.decart.ai.
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 Decart here at once, the problem is on Decart'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 Decart. 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.