Tripleseat Outage History

24 incidents recorded over the last 365 days, 24 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Tripleseat status100.00% uptime history

Every Recorded Tripleseat Incident

Tripleseat incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 27, 2026Login Issues4h 17mResolved
Oct 22, 2026Intermittent SMS 2-Factor Authentication Delays3h 25mResolved
Oct 10, 2026Login Issues1h 46mResolved
Sep 30, 2026Signature/Countersignature Fields Unavailable on Event/Booking Documents32 minResolved
Sep 30, 2026Document PDFs not generating/exporting and visual formatting Issues39 minResolved
Sep 24, 2026Users Auto CC'd on Discussions24h 38mResolved
Sep 14, 2026Lead Reports Loading Issues5h 49mResolved
Sep 11, 2026Generalized Slowness1h 14mResolved
Aug 15, 2026Sendgrid - Elevated IP Blocks to MS365 Users46h 46mResolved
Aug 7, 2026Document Templates Degraded Performance73h 20mResolved
Aug 3, 2026Insights Report Timeouts4h 14mResolved
Jul 29, 2026Login page unresponsive/missing credential fields22h 38mResolved
Jul 25, 2026Tickets2h 2mResolved
Jun 11, 2026Tripleseat44 minResolved
May 28, 2026Tripleseat1h 15mResolved
May 13, 2026EventUp59 minResolved
Apr 22, 2026Microsoft Edge Users: SmartScreen Warning on PDFs23h 37mResolved
Apr 17, 2026Dark Mode Text Display Issue4h 31mResolved
Feb 27, 2026Loading Issues on Safari70h 59mResolved
Feb 26, 2026Delivery Status Update Delays188h 12mResolved
Feb 10, 2026Some Tripleseat Assets Unavailable1h 27mResolved
Feb 6, 2026Menu Item Totals missing from Layouts, Grand Totals Skewed4h 27mResolved
Feb 4, 2026PDF Formatting Discrepancies16h 54mResolved
Jan 22, 2026Microsoft Outage - Email Deferrals19h 34mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Tripleseat incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Tripleseat Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Tripleseat acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Tripleseat outage in this window ran 7d 20h, against a mean recovery of 21h 50m. If you depend on Tripleseat in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.