Tigris outage, 14 July 2026

Investigating Increased Error Rate

Started
Resolved
15 Jul 2026, 20:30 UTC (after 37 h 23 min)
Impact
Minor

Last update from Tigris

Around **02:55-03:05 AM EDT**, some customers with traffic through **Johannesburg** may have seen elevated temporary write failures (`503` / SlowDown). Impact was regional and self-limiting. Error rates recovered shortly afterward, and we continue to monitor.

15 Jul 2026, 20:30 UTC

Is Tigris down now?

This page is the record of one past incident. For the live status, see Is Tigris down right now? - it reads the official status page every 2 minutes.

Other Tigris incidents

  1. Increased latencies in Tokyo

  2. Increased error rates in San Jose

  3. Outage in San Jose region

  4. Partial outage in US regions

  5. Increased error rates in London

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

  7. Increased error rates in Sao Paulo

  8. Increased latencies in San Jose

All recorded Tigris incidents