User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
zilliz.com · Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 495 ms · 5 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 05:15 | 0 | 0.0 | 944 ms | 0 |
| 05:30 | 0 | 0.0 | 478 ms | 0 |
| 05:45 | 0 | 0.0 | 1344 ms | 0 |
| 06:00 | 0 | 0.0 | 523 ms | 0 |
| 06:15 | 0 | 0.0 | 1104 ms | 0 |
| 06:30 | 0 | 0.0 | 873 ms | 0 |
| 06:45 | 0 | 0.0 | 903 ms | 0 |
| 07:00 | 0 | 0.0 | 1325 ms | 0 |
| 07:15 | 0 | 0.0 | 1470 ms | 0 |
| 07:30 | 0 | 0.0 | 906 ms | 0 |
| 07:45 | 0 | 0.0 | 1211 ms | 0 |
| 08:00 | 0 | 0.0 | 585 ms | 0 |
| 08:15 | 0 | 0.0 | 910 ms | 0 |
| 08:30 | 0 | 0.0 | 532 ms | 0 |
| 08:45 | 0 | 0.0 | 491 ms | 0 |
| 09:00 | 0 | 0.0 | 909 ms | 0 |
| 09:15 | 0 | 0.0 | 507 ms | 0 |
| 09:30 | 0 | 0.0 | 844 ms | 0 |
| 09:45 | 0 | 0.0 | 538 ms | 0 |
| 10:00 | 0 | 0.0 | 1236 ms | 0 |
| 10:15 | 0 | 0.0 | 932 ms | 0 |
| 10:30 | 0 | 0.0 | 1167 ms | 0 |
| 10:45 | 0 | 0.0 | 684 ms | 0 |
| 11:00 | 0 | 0.0 | 835 ms | 0 |
| 11:15 | 0 | 0.0 | 1344 ms | 0 |
| 11:30 | 0 | 0.0 | 1256 ms | 0 |
| 11:45 | 0 | 0.0 | 751 ms | 0 |
| 12:00 | 0 | 0.0 | 421 ms | 0 |
| 12:15 | 0 | 0.0 | 597 ms | 0 |
| 12:30 | 0 | 0.0 | 858 ms | 0 |
| 12:45 | 0 | 0.0 | 1174 ms | 0 |
| 13:00 | 0 | 0.0 | 606 ms | 0 |
| 13:15 | 0 | 0.0 | 1140 ms | 0 |
| 13:30 | 0 | 0.0 | 880 ms | 0 |
| 13:45 | 0 | 0.0 | 1626 ms | 0 |
| 14:00 | 0 | 0.0 | 1205 ms | 0 |
| 14:15 | 0 | 0.0 | 756 ms | 0 |
| 14:30 | 0 | 0.0 | 655 ms | 0 |
| 14:45 | 0 | 0.0 | 869 ms | 0 |
| 15:00 | 0 | 0.0 | 1198 ms | 0 |
| 15:15 | 0 | 0.0 | 354 ms | 0 |
| 15:30 | 0 | 0.0 | 805 ms | 0 |
| 15:45 | 0 | 0.0 | 1604 ms | 0 |
| 16:00 | 0 | 0.0 | 1229 ms | 0 |
| 16:15 | 0 | 0.0 | 743 ms | 0 |
| 16:30 | 0 | 0.0 | 1340 ms | 0 |
| 16:45 | 0 | 0.0 | 562 ms | 0 |
| 17:00 | 0 | 0.0 | 495 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Illiz 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 Illiz goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Illiz alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Illiz is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Illiz's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.