Truefoundry Outage History

6 incidents recorded over the last 365 days, 6 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 Truefoundry status99.94% uptime history

Every Recorded Truefoundry Incident

Truefoundry incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 12, 2026Gateway failed to assume role574h 13mResolved
Sep 18, 2026User login page erroring out1145h 8mResolved
Aug 24, 2026Control plane APIs degraded1645h 18mResolved
Jul 16, 2026Logins and signups are failing1839h 26mResolved
Jul 15, 2026Some of the requests on Truefoundry control plane UI are getting timed out1857h 52mResolved
Jun 5, 2026Control Plane APIs failing with intermittent 500 errors2097h 12mResolved

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 Truefoundry 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 Truefoundry 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 Truefoundry 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 Truefoundry outage in this window ran 87d 9h, against a mean recovery of 63d 14h. If you depend on Truefoundry 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.