Chroma - Notice history

All systems operational

API - Operational

100% - uptime
Aug 2025 · 99.97%Sep · 100.0%Oct · 99.68%

Previous page

Next page

Aug 2025
Sep 2025
Oct 2025

Dashboard - Operational

100% - uptime
Aug 2025 · 99.97%Sep · 100.0%Oct · 99.85%

Previous page

Next page

Aug 2025
Sep 2025
Oct 2025

Package Search MCP - Operational

100% - uptime
Aug 2025 · 100.0%Sep · 99.86%Oct · 99.85%

Previous page

Next page

Aug 2025
Sep 2025
Oct 2025

Notice history

Oct 2025

AWS incident is us-east-1
  • Resolved
    Resolved

    AWS had an incident in us-east-1 which affected all requests to Chroma between 7:00 10/20/25 through 9:10 10/20/25 UTC. During this period, some API routes returned 500 status codes. The incident has now resolved and we see no more customer impact. https://health.aws.amazon.com/health/status

  • Monitoring
    Monitoring

    AWS has an incident in us-east-1 which affects all requests to Chroma. Some API routes are returning 500 status codes.

Queries may fail
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.

Sep 2025

Package Search MCP
  • Resolved
    Resolved

    We've identified and fixed it

  • Investigating
    Investigating
    We are currently investigating this incident.

Aug 2025

All API requests
  • Resolved
    Resolved

    This incident has been resolved. A faulty change was rolled out to our authentication system, the implicated change has been rolled back.

  • Investigating
    Investigating
    We are currently investigating this incident.
Increase in billing data latency
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    Our billing data pipeline is currently processing events slower than targeted. Billing data may be slightly behing.

Aug 2025 to Oct 2025

Next