Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

TigerData Outage History

Every past TigerData outage tracked by IsDown, with detection times, duration, and resolution details.

There were 76 TigerData outages since May 2023. The 36 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor March 23, 2026

March 2026: Degraded Insights Metrics on console

Detected Mar 23, 2026 8:41 PM EDT · Resolved Mar 26, 2026 10:40 AM EDT · Duration 3 days

Timescale experienced degraded Insights metrics on their console due to an issue during a database upgrade, causing delays and gaps in metric processing while data ingestion continued normally. Database services remained fully operational throughout the incident. The team restored data for the most recent 24 hours and continued backfilling historical data to resolve remaining gaps from earlier time ranges.

Maintenance March 3, 2026

March 2026: Scheduled Maintenance 2026-03-09 - 2026-03-16

Detected Mar 3, 2026 7:13 AM EST · Resolved Mar 16, 2026 1:04 AM EDT · Duration 13 days

Timescale performed scheduled maintenance on TigerData services across 7 regions from March 9-16, 2026, involving instance restarts and PostgreSQL minor version updates (18.3, 17.9, 16.13, 15.17). Services with HA replicas experienced only brief switchover events lasting seconds, while services without HA replicas had downtime during their maintenance windows. The maintenance was completed over a 7-day period with no user action required.

Maintenance March 3, 2026

March 2026: Scheduled Maintenance 2026-03-16 - 2026-03-23

Detected Mar 3, 2026 7:05 AM EST · Resolved Mar 23, 2026 1:05 AM EDT · Duration 20 days

Timescale performed scheduled maintenance on TigerData services across multiple regions from March 16-23, 2026, involving instance restarts and PostgreSQL minor version updates (18.3, 17.9, 16.13, 15.17). Services with HA replicas experienced only brief switchover events lasting a few seconds, while services without HA replicas had downtime during their maintenance windows.

Maintenance March 3, 2026

March 2026: Scheduled Maintenance 2026-03-09 - 2026-03-16

Detected Mar 3, 2026 6:35 AM EST · Resolved Mar 3, 2026 7:10 AM EST · Duration 35 minutes

Timescale performed scheduled maintenance on TigerData services across seven regions from March 9-16, 2026, involving instance restarts and PostgreSQL minor version updates (18.3, 17.9, 16.13, 15.17). Services with HA replicas experienced only brief switchover events lasting a few seconds, while services without HA replicas had downtime during their maintenance windows.

Minor February 26, 2026

February 2026: Investigating Network Connectivity

Detected Feb 26, 2026 1:42 PM EST · Resolved Feb 26, 2026 2:04 PM EST · Duration 22 minutes

Timescale experienced network connectivity issues affecting a limited number of services in a degraded connection state. The incident was classified as minor and lasted 22 minutes. The issue was resolved without further details provided about the specific resolution method.

Maintenance February 26, 2026

February 2026: TimescaleDB 2.25.1 Release

Detected Feb 26, 2026 7:40 AM EST · Resolved Mar 9, 2026 2:03 AM EDT · Duration 11 days

TimescaleDB 2.25.1 was released as a scheduled maintenance update, bringing various improvements, bug fixes, and enhancements to the time-series database platform. The upgrade was automatically deployed to development databases during their configured maintenance windows starting March 2, 2026, with production databases receiving the update three weeks later. The maintenance was completed successfully over approximately 10.7 days as part of the phased rollout process.

Minor February 23, 2026

February 2026: Service creation is not working

Detected Feb 23, 2026 12:14 PM EST · Resolved Feb 23, 2026 12:59 PM EST · Duration 44 minutes

Timescale Cloud experienced an issue with a problematic API call that prevented new services from being created for 44 minutes. Existing running services were not affected during this incident. The team actively worked on and resolved the API issue.