Tiger Cloud & Tiger Data Status

Tiger Cloud & Tiger Data Status

All Systems Operational

Check the current status and uptime of Tiger Cloud and Tiger Data. View live service health, active incidents, and scheduled maintenance

Scheduled maintenance
Published Nov 17, 2026 2:14 PM UTC

November Maintenance Event

Scheduled for Nov 23, 2026 6:00 AM UTC - Nov 30, 2026 6:00 AM UTC

Advisory: Defer manual upgrades to TimescaleDB 2.32.1

If you run an existing Tiger Cloud service, we recommend waiting to upgrade to TimescaleDB 2.32.1 unless you have a specific need for this version. The highest TimescaleDB version included in automatic upgrades is 2.31.2. We will not automatically upgrade any service to 2.32.1.

New services use TimescaleDB 2.32.1 by default. Services created on 2.32.1 are unaffected by this issue and require no action.

How the issue affects upgraded services

An existing service upgraded to 2.32.1 from an earlier version may encounter write failures. When TimescaleDB creates a new chunk, it uses the hypertable owner’s privileges to create foreign key constraints. If that owner lacks the required REFERENCES privilege on a referenced table, an insert that requires a new chunk can fail. Inserts into existing chunks can continue to succeed.

What to do if you upgrade manually

  • If you need to upgrade to 2.32.1 now, check the privileges described below and grant any that are missing before upgrading.
  • If you have already upgraded manually, check those privileges and grant any that are missing now, even if inserts are still succeeding. If an insert failed because of this issue, retry it after applying the grant.

For each foreign key on a hypertable, check whether the hypertable owner has the required REFERENCES privilege on the referenced table. Where the privilege is missing, run the following command as the referenced table’s owner or another role authorized to grant it.

GRANT REFERENCES ON TABLE <schema>.<referenced_table> TO <hypertable_owner>;

Replace the placeholders with the actual schema, referenced table, and hypertable owner. Repeat for each referenced table on which that owner lacks the required privilege.

If you are unsure whether your service is affected or need assistance, please contact Tiger Cloud support and reference this advisory. We will update this page as a resolution becomes available.


Scheduled Maintenance

We will be performing maintenance on TigerData services in all regions to deploy PostgreSQL security updates, apply TimescaleDB compatibility patches, and update database certificates.

Maintenance will begin on November 23, 2026 at 06:00 AM UTC. Your service will undergo maintenance within its configured maintenance window.

What to expect

  • All services will restart within their scheduled maintenance window, regardless of their environment tag (dev or production).
  • No action is required to receive these maintenance updates.
  • Services without HA replicas will experience a brief interruption while their databases restart.
  • Services with HA replicas will undergo a single switchover event during maintenance, typically lasting a few seconds. Connections may be briefly interrupted during the switchover.
  • To minimize downtime during this maintenance, consider adding an HA replica to your service.

PostgreSQL security updates

We will roll out PostgreSQL minor versions 18.7, 17.12, and 16.16 for services running the corresponding PostgreSQL major versions. These updates focus on addressing a wide range of security vulnerabilities and also include bug fixes and reliability improvements.

For more details, see the PostgreSQL release announcement and release notes.

TimescaleDB compatibility patches

Alongside the PostgreSQL updates, we will deploy TimescaleDB patch releases 2.27.3, 2.28.5, 2.29.3, 2.30.3, and 2.31.2 across the corresponding supported TimescaleDB release series. Release notes will be available once the corresponding releases are done.

TimescaleDB 2.32.1 also includes the compatibility fix. It is the default for new services and is excluded from automatic upgrades, as described in the advisory above.

This rollout differs from a regular TimescaleDB release. The new PostgreSQL minor versions introduce a compatibility change that prevents TimescaleDB background workers from functioning correctly without a corresponding patch. To ensure continued operation, we have backported the compatibility fix to all supported TimescaleDB release series listed above.

These patches allow services to receive the PostgreSQL security updates while remaining on their existing supported TimescaleDB release series.

Database certificate updates

Database TLS certificates will use a wildcard in place of the service ID in the hostname, replacing certificates that explicitly list each service's fully qualified domain name.

No action is required for this certificate change. Your existing database hostname and connection settings will continue to work seamlessly. The chain of trust remains unchanged, so you do not need to download or install a new certificate chain.

If you have any questions, please reach out to our support team.

System Status

Jan 18, 1656 - Mar 17, 1656

Database - Data Plane and Core Availability

· --% uptime
Jan 18, 1656
Mar 17, 1656

Database - Control Plane Actions (create, resize, resume, etc)

· --% uptime
Jan 18, 1656
Mar 17, 1656

Data Protection & Recovery

· --% uptime
Jan 18, 1656
Mar 17, 1656

Data Movement & Connectors

· --% uptime
Jan 18, 1656
Mar 17, 1656

Console & API

· --% uptime
Jan 18, 1656
Mar 17, 1656

Observability

· --% uptime
Jan 18, 1656
Mar 17, 1656
Incident history