Tigris outage, 23 October 2026

Partial outage and elevated errors in US East

Started
Resolved
23 Oct 2026, 19:50 UTC (after 56 min)
Impact
Major

Is this still happening?

No. Tigris marked this incident resolved on 23 Oct 2026, 19:50 UTC, 56 min after it began.

Right now: Tigris reports all systems operational. (as of 26 Oct, 03:47 UTC) Live Tigris status

Last update from Tigris

On October 23, 2026, between 18:39 and 19:40 UTC, customers using our US East region experienced failed requests and elevated latency. A memory accounting error on some of our servers caused them to run out of memory during routine provisioning, which disrupted request handling in that region. The issue has been resolved and we have no indication of data loss. We are making changes to prevent this from happening again.

24 Oct 2026, 03:09 UTC

Similar Tigris incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 1 h 9 min

    Elevated Error Rate in US East and Central

Other recent Tigris incidents

  1. Investigating performance issues

  2. Increased latencies in Tokyo

  3. Increased error rates in San Jose

  4. Outage in San Jose region

  5. Partial outage in US regions

  6. Increased error rates in London

  7. Increased latencies in Ashburn/IAD Region for users in AWS

  8. Increased error rates in Sao Paulo

All recorded Tigris incidents