Trint Outage History

18 incidents recorded over the last 365 days, 17 of them resolved, 1 still open. 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 Trint status100.00% uptime history

Every Recorded Trint Incident

Trint incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 20, 2026Delays in transcription of new uploadsThe incident has been resolved.—Investigating
Sep 21, 2026Issue starting new real time streamsThis incident has been resolved.39 minResolved
Jul 10, 2026Service degraded in USThis incident has been resolved.38 minResolved
Jun 30, 2026Transcription outageThis incident has been resolved.4h 3mResolved
Jun 18, 2026Transcription processing delaysThis incident has been resolved.43 minResolved
Jun 17, 2026Increased transcription timesThis incident has been resolved.38 minResolved
Jun 13, 2026Trint platform EU tenant degradedAn intermittent service interruption began at 6:45am and ended at 8:05am.0 minResolved
Jun 1, 2026Partial outage for realtime transcription in the US and EU tenantsThis incident has been resolved.1h 51mResolved
Apr 23, 2026Real time push from webappUsers are unable to start push realtimes from the webapp-9990 minResolved
Apr 8, 2026Slower transcription timesSome users experienced longer than average transcription times-11094 minResolved
Feb 26, 2026Uploads through the webappThis incident has been resolved.2h 13mResolved
Feb 25, 2026Transcription FailuresThis incident has been resolved.58 minResolved
Feb 10, 2026Trint platform US tenant degradedDegraded performance and intermittent errors across the platform.-166 minResolved
Dec 8, 2025Reports with realtime transcriptionWe are happy this has been resovled14h 29mResolved
Dec 3, 2025Upload functionality degraded in US tenantA subset of users on the US tenant were unable to upload or transcribe files. A transcription limit model was displayed incorrectly indicating their account limit had been reached and blocking the upload and…-19672 minResolved
Nov 13, 2025Upload API outage (EU region)Upload API outage (EU region)-10532 minResolved
Nov 13, 2025Upload API outage (EU region)Upload API outage experienced in EU region0 minResolved
Nov 5, 2025EU enterprise customers unable to playback on new realtime streamsEU enterprise customers were temporarily unable to playback video on new realtime streams.-1896 minResolved

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 Trint 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 Trint 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 Trint 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 Trint outage in this window ran 14h 29m, against a mean recovery of 2h 23m. If you depend on Trint 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.