User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Chroma down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → trychroma.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 336 ms.
Official status
All clear
All systems operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 473 ms | 0 |
| Mon 19 | 0 | 0.0 | 258 ms | 0 |
| Mon 21 | 0 | 0.0 | 364 ms | 0 |
| Mon 23 | 0 | 0.0 | 319 ms | 0 |
| Tue 01 | 0 | 0.0 | 294 ms | 0 |
| Tue 03 | 0 | 0.0 | 316 ms | 0 |
| Tue 05 | 0 | 0.0 | 171 ms | 0 |
| Tue 07 | 0 | 0.0 | 429 ms | 0 |
| Tue 09 | 0 | 0.0 | 471 ms | 0 |
| Tue 11 | 0 | 0.0 | 399 ms | 0 |
| Tue 14 | 0 | 0.0 | 476 ms | 0 |
| Tue 16 | 0 | 0.0 | 353 ms | 0 |
| Tue 18 | 0 | 0.0 | 352 ms | 0 |
| Tue 20 | 0 | 0.0 | 188 ms | 0 |
| Tue 23 | 0 | 0.0 | 285 ms | 0 |
| Wed 01 | 0 | 0.0 | 372 ms | 0 |
| Wed 03 | 0 | 0.0 | 484 ms | 0 |
| Wed 05 | 0 | 0.0 | 462 ms | 0 |
| Wed 08 | 0 | 0.0 | 399 ms | 0 |
| Wed 10 | 0 | 0.0 | 448 ms | 0 |
| Wed 12 | 0 | 0.0 | 372 ms | 0 |
| Wed 14 | 0 | 0.0 | 357 ms | 0 |
| Wed 16 | 0 | 0.0 | 329 ms | 0 |
| Wed 18 | 0 | 0.0 | 369 ms | 0 |
| Wed 21 | 0 | 0.0 | 585 ms | 0 |
| Wed 23 | 0 | 0.0 | 467 ms | 0 |
| Thu 01 | 0 | 0.0 | 247 ms | 0 |
| Thu 03 | 0 | 0.0 | 200 ms | 0 |
| Thu 05 | 0 | 0.0 | 486 ms | 0 |
| Thu 07 | 0 | 0.0 | 391 ms | 0 |
| Thu 09 | 0 | 0.0 | 173 ms | 0 |
| Thu 11 | 0 | 0.0 | 388 ms | 0 |
| Thu 13 | 0 | 0.0 | 102 ms | 0 |
| Thu 15 | 0 | 0.0 | 321 ms | 0 |
| Thu 17 | 0 | 0.0 | 312 ms | 0 |
| Thu 19 | 0 | 0.0 | 135 ms | 0 |
| Thu 21 | 0 | 0.0 | 579 ms | 0 |
| Fri 00 | 0 | 0.0 | 374 ms | 0 |
| Fri 02 | 0 | 0.0 | 453 ms | 0 |
| Fri 04 | 0 | 0.0 | 143 ms | 0 |
| Fri 06 | 0 | 0.0 | 254 ms | 0 |
| Fri 08 | 0 | 0.0 | 445 ms | 0 |
| Fri 10 | 0 | 0.0 | 297 ms | 0 |
| Fri 11 | 0 | 0.0 | 139 ms | 0 |
| Fri 12 | 0 | 0.0 | 476 ms | 0 |
| Fri 14 | 0 | 0.0 | 382 ms | 0 |
| Fri 16 | 0 | 0.0 | 320 ms | 0 |
| Fri 18 | 0 | 0.0 | 336 ms | 0 |
Reliability
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.
Embed this status: free live Chroma badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Chroma yet. Outages of 10 minutes or more get their own page here.
Having trouble with Chroma?
One report per service every 10 minutes from this network. No account.
Follow Chroma
Get an email when Chroma goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Chroma alerts to Slack, Discord or a webhook — free.
About Chroma
Chroma is listed in our AI category and checked at trychroma.com. Open-source search infrastructure for AI
Chroma publishes an official status page at status.trychroma.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: 339 ms average, 47–799 ms range across 15 successful checks.
Questions
Is Chroma down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Chroma last down?
We have not recorded a public Chroma incident since monitoring began 8 days ago.
What is Chroma's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Chroma respond?
339 ms on average over the last 24 hours (47–799 ms).
Does Chroma have an official status page?
Yes, at https://status.trychroma.com.
Chroma not working for me but the status is fine. What now?
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 Chroma here at once, the problem is on Chroma'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 Chroma. 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.