TigerData Outage History

TigerData had 4 outages in the last 2 years — averaging 0.2 incidents per month.

There were 4 TigerData outages since March 27, 2026. Each is summarised below — incident details, duration, and resolution information.

Minor May 28, 2026

Slow deployments in one region

Timeline · 3 updates

investigating May 28, 2026, 04:26 PM UTC

We are currently investigating an issue where new service deployments in east-us-1 region is slower then expected.
identified May 28, 2026, 04:58 PM UTC

We have been investigating an issue where new service deployments in east-us-1 region are slower then expected. Current status is that new service creation is back to normal.
resolved May 28, 2026, 05:05 PM UTC

Situation mitigated, new services are now being deployed as expected.

Minor May 19, 2026

Timeline · 3 updates

investigating May 19, 2026, 03:52 AM UTC

We are currently experiencing issues with users attempting to log into the console. The investigation is ongoing. Database services are not affected.
monitoring May 19, 2026, 04:04 AM UTC

Console login functionality has been restored and should now be working normally again, and the console service is currently under monitoring. We’re continuing to investigate the underlying root cause to better understand what triggered the issue.
resolved May 19, 2026, 04:26 AM UTC

This incident has now been fully resolved and console login functionality is operating normally again. Our investigation identified the issue as being related to an upstream FusionAuth maintenance activity that temporarily impacted authentication flows. Database services remained fully operational throughout the incident.

Minor April 21, 2026

Timeline · 2 updates

resolved Apr 21, 2026, 02:00 PM UTC

Out of memory issues have been addressed by the new proxy release
resolved Apr 29, 2026, 07:15 PM UTC

Out of memory issues have been addressed by the new release

Minor March 27, 2026

Affected: Tiger Data service

Timeline · 1 update

resolved Mar 27, 2026, 04:03 PM UTC

Database was stabilised and the incident is resolved