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 28 min ago. Last stored result reached it in 58 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 55 ms | 0 |
| Tue 00 | 0 | 0.0 | 140 ms | 0 |
| Tue 02 | 0 | 0.0 | 92 ms | 0 |
| Tue 05 | 0 | 0.0 | 42 ms | 0 |
| Tue 07 | 0 | 0.0 | 100 ms | 0 |
| Tue 09 | 0 | 0.0 | 106 ms | 0 |
| Tue 11 | 0 | 0.0 | 70 ms | 0 |
| Tue 13 | 0 | 0.0 | 176 ms | 0 |
| Tue 15 | 0 | 0.0 | 81 ms | 0 |
| Tue 18 | 0 | 0.0 | 91 ms | 0 |
| Tue 20 | 0 | 0.0 | 96 ms | 0 |
| Tue 22 | 0 | 0.0 | 119 ms | 0 |
| Wed 00 | 0 | 0.0 | 56 ms | 0 |
| Wed 03 | 0 | 0.0 | 125 ms | 0 |
| Wed 05 | 0 | 0.0 | 52 ms | 0 |
| Wed 07 | 0 | 0.0 | 72 ms | 0 |
| Wed 09 | 0 | 0.0 | 81 ms | 0 |
| Wed 12 | 0 | 0.0 | 73 ms | 0 |
| Wed 14 | 0 | 0.0 | 68 ms | 0 |
| Wed 16 | 0 | 0.0 | 101 ms | 0 |
| Wed 18 | 0 | 0.0 | 100 ms | 0 |
| Wed 20 | 0 | 0.0 | 158 ms | 0 |
| Wed 22 | 0 | 0.0 | 220 ms | 0 |
| Thu 01 | 0 | 0.0 | 110 ms | 0 |
| Thu 03 | 0 | 0.0 | 131 ms | 0 |
| Thu 05 | 0 | 0.0 | 88 ms | 0 |
| Thu 07 | 0 | 0.0 | 152 ms | 0 |
| Thu 09 | 0 | 0.0 | 99 ms | 0 |
| Thu 11 | 0 | 0.0 | 91 ms | 0 |
| Thu 13 | 0 | 0.0 | 156 ms | 0 |
| Thu 15 | 0 | 0.0 | 31 ms | 0 |
| Thu 17 | 0 | 0.0 | 72 ms | 0 |
| Thu 19 | 0 | 0.0 | 123 ms | 0 |
| Thu 21 | 0 | 0.0 | 68 ms | 0 |
| Thu 23 | 0 | 0.0 | 63 ms | 0 |
| Fri 01 | 0 | 0.0 | 96 ms | 0 |
| Fri 03 | 0 | 0.0 | 70 ms | 0 |
| Fri 05 | 0 | 0.0 | 66 ms | 0 |
| Fri 07 | 0 | 0.0 | 70 ms | 0 |
| Fri 09 | 0 | 0.0 | 87 ms | 0 |
| Fri 10 | 0 | 0.0 | 51 ms | 0 |
| Fri 12 | 0 | 0.0 | 78 ms | 0 |
| Fri 14 | 0 | 0.0 | 60 ms | 0 |
| Fri 16 | 0 | 0.0 | 100 ms | 0 |
| Fri 18 | 0 | 0.0 | 73 ms | 0 |
| Fri 20 | 0 | 0.0 | 30 ms | 0 |
| Fri 21 | 0 | 0.0 | 58 ms | 0 |
| Fri 22 | 0 | 0.0 | 94 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.
[Korea Region] Database Maintenance
On Monday, November 16 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure AI Platform. These updates are necessary to ensure we have the latest security and performance improvements available. There may be a brief period of unavailability…
[US Region] Database Maintenance
On Tuesday, November 17 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure AI Platform. These updates are necessary to ensure we have the latest security and performance improvements available. There may be a brief period of unavailability…
[Tokyo Region] Database Maintenance
On Wednesday, November 18 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure AI Platform. These updates are necessary to ensure we have the latest security and performance improvements available. There may be a brief period of unavailability…
[AP03 Region] Database Maintenance
On Thursday, November 19 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure AI Platform. These updates are necessary to ensure we have the latest security and performance improvements available. There may be a brief period of unavailability…
[EU Region] Database Maintenance
On Friday, November 20 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by the Treasure AI Platform. These updates are necessary to ensure we have the latest security and performance improvements available. There may be a brief period of unavailability…
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Treasure AI 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 Treasure AI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Treasure AI alerts to Slack, Discord or a webhook — free.
We track Treasure AI (treasure.ai) as part of the AI group. Treasure AI is the Agentic Experience Platform built to acquire, retain, and grow your most valuable customers, powered by AI, shaped by human creativity, and always-on through continuous, context-driven action. See why Forrester named us a Leader.
Treasure AI publishes an official status page at status.treasure.ai; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 72 ms average, 30–112 ms range across 18 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Treasure AI incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
72 ms on average over the last 24 hours (30–112 ms).
Yes, at https://status.treasure.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 Treasure AI here at once, the problem is on Treasure AI'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 Treasure AI. 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.