User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
exasol.com · 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 41 min ago. Last stored result reached it in 776 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 845 ms | 0 |
| Nov 7 | 0 | 0.0 | 760 ms | 0 |
| Nov 7 | 0 | 0.0 | 805 ms | 0 |
| Nov 7 | 0 | 0.0 | 785 ms | 0 |
| Nov 8 | 0 | 0.0 | 730 ms | 0 |
| Nov 8 | 0 | 0.0 | 740 ms | 0 |
| Nov 8 | 0 | 0.0 | 783 ms | 0 |
| Nov 8 | 0 | 0.0 | 797 ms | 0 |
| Nov 9 | 0 | 0.0 | 800 ms | 0 |
| Nov 9 | 0 | 0.0 | 709 ms | 0 |
| Nov 9 | 0 | 0.0 | 794 ms | 0 |
| Nov 9 | 0 | 0.0 | 1176 ms | 0 |
| Nov 10 | 0 | 0.0 | 758 ms | 0 |
| Nov 10 | 0 | 0.0 | 1329 ms | 0 |
| Nov 10 | 0 | 0.0 | 810 ms | 0 |
| Nov 10 | 0 | 0.0 | 819 ms | 0 |
| Nov 11 | 0 | 0.0 | 740 ms | 0 |
| Nov 11 | 0 | 0.0 | 800 ms | 0 |
| Nov 11 | 0 | 0.0 | 694 ms | 0 |
| Nov 11 | 0 | 0.0 | 816 ms | 0 |
| Nov 12 | 0 | 0.0 | 782 ms | 0 |
| Nov 12 | 0 | 0.0 | 797 ms | 0 |
| Nov 12 | 0 | 0.0 | 731 ms | 0 |
| Nov 12 | 0 | 0.0 | 763 ms | 0 |
| Nov 13 | 0 | 0.0 | 594 ms | 0 |
| Nov 13 | 0 | 0.0 | 675 ms | 0 |
| Nov 13 | 0 | 0.0 | 795 ms | 0 |
| Nov 13 | 0 | 0.0 | 796 ms | 0 |
| Nov 14 | 0 | 0.0 | 712 ms | 0 |
| Nov 14 | 0 | 0.0 | 754 ms | 0 |
| Nov 14 | 0 | 0.0 | 759 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 Exasol SaaS 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 Exasol SaaS goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
Exasol SaaS is listed in our AI category and checked at exasol.com. Discover Exasol: modernize data warehouses, accelerate analytics, optimize costs, and run governed AI/ML models—powered by Exasol’s analytics database.
Exasol SaaS publishes an official status page at status.exasol.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: 763 ms average, 522–958 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 Exasol SaaS incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
763 ms on average over the last 24 hours (522–958 ms).
Yes, at https://status.exasol.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 Exasol SaaS here at once, the problem is on Exasol SaaS'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 Exasol SaaS. 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.