Tigris outage history
25 incidents from the official Tigris status page, the oldest from 16 February 2025.
August 2026 3
-
, resolved after 5 min
Impact: major
-
, resolved after 5 min
Increased error rates in San Jose
Impact: major
-
, resolved after 1 h
Impact: critical
July 2026 16
-
, resolved after 1 h 33 min
Impact: major
-
, resolved after 5 min
Increased error rates in London
Impact: major
-
, resolved after 2 h 34 min
Increased latencies in Ashburn/IAD Region for users in AWS
Impact: minor
-
, resolved after 10 min
Increased error rates in Sao Paulo
Impact: major
-
, resolved after 24 min
Increased latencies in San Jose
Impact: major
-
, resolved after 4 min
Increased latencies in San Jose
Impact: major
-
, resolved after 4 min
Increased latencies in San Jose
Impact: major
-
, resolved after 24 min
Increased latencies in San Jose
Impact: major
-
, resolved after 1 h 16 min
Increased latencies in San Jose
Impact: major
-
, resolved after 7 min
Impact: minor
-
, resolved after 37 h 23 min
Investigating Increased Error Rate
Impact: minor
-
, resolved after 15 min
-
, resolved after 24 min
Investigating Increased Error Rate in IAD region
Impact: minor
-
, resolved after 2 h 30 min
-
, resolved after 4 h 35 min
US Fly customers may experience increased error rate
Impact: major
-
, resolved after 11 h 53 min
Customers configured to use a single region of SJC may experience 404s due to replication delays
Impact: minor
May 2026 2
-
, resolved after 43 min
Increased Error Rate for Fly Customers in Singapore
Impact: minor
-
, resolved after 20 min
April 2026 1
-
, resolved after 1 h 9 min
Elevated Error Rate in US East and Central
Impact: major
March 2026 1
-
, resolved after 8 h 50 min
January 2026 1
-
, resolved after 3 h 28 min
February 2025 1
-
, resolved after 3 h 36 min
Experiencing connectivity issues in all regions
Impact: major