Outage report · Major outage

Tripleseat outage on Feb 10, 2026

New incident: "Some Tripleseat Assets Unavailable"

SeverityMajor outage

StartedFeb 10, 2026, 21:08UTC

ResolvedFeb 11, 2026, 21:49UTC

Duration1d

What happened

Tripleseat reported a major outage starting Feb 10, 2026, 21:08 UTC. It was marked resolved at Feb 11, 2026, 21:49 UTC.

The incident lasted 1d from first report to resolution.
Tripleseat had reported 1 other partial or major outage in the 90 days before it.
8 other vendors we track reported a significant incident within 12 hours of it.

Latest update from Tripleseat

Milestone is now 'closed'. Previously milestone was 'postmortem_completed' Milestone is now 'postmortem_completed'. Previously milestone was 'postmortem_started' Milestone is now 'postmortem_started'. Previously milestone was 'resolved' Milestone is now 'resolved'. Previously milestone was 'mitigated' The Cloudfront team has deployed an update to mitigate the issues reported on their Status Page (https://health.aws.amazon.com/health/status). They are still working on some affected regions. Some users may still encounter style discrepancies until Cloudfront's services are fully restored, however we are noticing an overall improvement in performance and previously missing assets are beginning to render as expected. We will continue monitoring Tripleseat to ensure this trend continues and that there are no residual impacts following Cloudfront's mitigations. Milestone is now 'mitigated'. Previously milestone was 'identified' Component 'Tripleseat' is now 'Operational' Our Developers have

Read Tripleseat's official incident report ↗