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 2 hr ago. Last stored result reached it in 27 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 228 ms | 0 |
| Mon 14 | 0 | 0.0 | 144 ms | 0 |
| Mon 16 | 0 | 0.0 | 141 ms | 0 |
| Mon 18 | 0 | 0.0 | 82 ms | 0 |
| Mon 20 | 0 | 0.0 | 280 ms | 0 |
| Mon 22 | 0 | 0.0 | 141 ms | 0 |
| Tue 00 | 0 | 0.0 | 357 ms | 0 |
| Tue 02 | 0 | 0.0 | 48 ms | 0 |
| Tue 04 | 0 | 0.0 | 27 ms | 0 |
| Tue 07 | 0 | 0.0 | 170 ms | 0 |
| Tue 09 | 0 | 0.0 | 394 ms | 0 |
| Tue 11 | 0 | 0.0 | 301 ms | 0 |
| Tue 13 | 0 | 0.0 | 190 ms | 0 |
| Tue 15 | 0 | 0.0 | 681 ms | 0 |
| Tue 18 | 0 | 0.0 | 109 ms | 0 |
| Tue 20 | 0 | 0.0 | 169 ms | 0 |
| Tue 22 | 0 | 0.0 | 158 ms | 0 |
| Wed 00 | 0 | 0.0 | 296 ms | 0 |
| Wed 03 | 0 | 0.0 | 216 ms | 0 |
| Wed 05 | 0 | 0.0 | 365 ms | 0 |
| Wed 07 | 0 | 0.0 | 70 ms | 0 |
| Wed 09 | 0 | 0.0 | 279 ms | 0 |
| Wed 12 | 0 | 0.0 | 331 ms | 0 |
| Wed 14 | 0 | 0.0 | 333 ms | 0 |
| Wed 16 | 0 | 0.0 | 64 ms | 0 |
| Wed 18 | 0 | 0.0 | 165 ms | 0 |
| Wed 20 | 0 | 0.0 | 217 ms | 0 |
| Wed 22 | 0 | 0.0 | 475 ms | 0 |
| Thu 01 | 0 | 0.0 | 108 ms | 0 |
| Thu 03 | 0 | 0.0 | 352 ms | 0 |
| Thu 04 | 0 | 0.0 | 122 ms | 0 |
| Thu 06 | 0 | 0.0 | 415 ms | 0 |
| Thu 08 | 0 | 0.0 | 58 ms | 0 |
| Thu 10 | 0 | 0.0 | 366 ms | 0 |
| Thu 12 | 0 | 0.0 | 374 ms | 0 |
| Thu 14 | 0 | 0.0 | 230 ms | 0 |
| Thu 16 | 0 | 0.0 | 87 ms | 0 |
| Thu 17 | 0 | 0.0 | 183 ms | 0 |
| Thu 19 | 0 | 0.0 | 215 ms | 0 |
| Thu 21 | 0 | 0.0 | 61 ms | 0 |
| Thu 23 | 0 | 0.0 | 77 ms | 0 |
| Fri 01 | 0 | 0.0 | 54 ms | 0 |
| Fri 03 | 0 | 0.0 | 272 ms | 0 |
| Fri 05 | 0 | 0.0 | 246 ms | 0 |
| Fri 08 | 0 | 0.0 | 98 ms | 0 |
| Fri 10 | 0 | 0.0 | 196 ms | 0 |
| Fri 11 | 0 | 0.0 | 220 ms | 0 |
| Fri 13 | 0 | 0.0 | 39 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 Sigma Computing 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 Sigma Computing goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Sigma Computing alerts to Slack, Discord or a webhook — free.
We track Sigma Computing (sigmacomputing.com) as part of the AI group. Build and run AI apps, dashboards, and agents on governed warehouse data. Sigma lets any team build with chat, a spreadsheet, SQL, or Python.
Sigma Computing publishes an official status page at status.sigmacomputing.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 142 ms average, 27–272 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Sigma Computing incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
142 ms on average over the last 24 hours (27–272 ms).
Yes, at https://status.sigmacomputing.com.
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 Sigma Computing here at once, the problem is on Sigma Computing'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 Sigma Computing. 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.