Tempo Outage History
21 incidents recorded over the last 365 days, 18 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.
Every Recorded Tempo Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | Scheduled Infrastructure Updates (US Region)Maintenance has started | — | Scheduled |
| Oct 27, 2026 | Scheduled Infrastructure Updates (EU region)Maintenance has started | 49h 23m | Resolved |
| Oct 19, 2026 | Production EKS Cluster Upgrade (Nexus) - prod-us-east-2We'll be doing scheduled maintenance to keep our platform secure and up to date. We don't expect any impact to the service, and we'll post an update here once the work is complete. | 1h 46m | Resolved |
| Oct 19, 2026 | Production EKS Cluster Upgrade (Nexus) - prod-us-east-2Updating infrastructure We'll be doing scheduled maintenance to keep our platform secure and up to date. We don't expect any impact to the service, and we'll post an update here once the work is complete. | 2h 0m | Scheduled |
| Oct 1, 2026 | Disruption to Atlassian servicesAtlassian has reported an incident which occured between 01:00 UTC and 07:25 UTC: <https://jira-software.status.atlassian.com/incidents/vwrp378v0zmk> This resulted in Tempo failing to load for many customers. The… | -752 min | Resolved |
| Sep 25, 2026 | Planned infrastructure maintenanceMaintenance in the US region has completed. | 6h 33m | Resolved |
| Sep 15, 2026 | Slow response times and elevated errorsThe incident has been resolved. During the incident we had to block Jira Issue webhook processing, but any updates in Jira since September 16th at 8:30pm have been processed normally. | 42h 30m | Resolved |
| Aug 27, 2026 | Tempo App UnavailabilityThis incident has been resolved. The affected Tempo apps have been restored and are operating normally for impacted customers. A fix has been deployed to prevent recurrence. If you're still experiencing issues, please… | 103h 23m | Resolved |
| Aug 25, 2026 | Degraded performanceThis incident has been resolved. | 6h 43m | Resolved |
| Jul 31, 2026 | Elevated API ErrorsThe issue has been resolved. | 7h 50m | Resolved |
| Jun 15, 2026 | Degraded performanceIncident has been resolved. | 2h 48m | Resolved |
| Jun 15, 2026 | Brief outageIncident has been resolved. | 2h 51m | Resolved |
| Jun 9, 2026 | Degraded performanceWe had some delay in event processing during last night, the issue has been resolved. | 7h 2m | Resolved |
| May 12, 2026 | Some users unable to use TempoOur customers are reporting that they're able to access Tempo now. | 19h 16m | Resolved |
| May 8, 2026 | Degraded performanceIncident has been resolved. | 7h 54m | Resolved |
| Apr 2, 2026 | Forge Migration UpdateThe migration of Timesheets, Capacity Planner, and Financial Manager to [Forge](https://www.tempo.io/product-news/tempo-moves-to-forge) is underway, but the **automatic rollout did not start on March 31, 2026 as… | — | Investigating |
| Mar 3, 2026 | Data Processing Delays - Reporting Tools AffectedWe have identified and addressed the root cause of the delays. The issue is now resolved. | 360h 36m | Resolved |
| Feb 26, 2026 | Elevated API ErrorsThe incident was resolved. Root cause analysis for a permanent solution is in progress. | 2h 4m | Resolved |
| Jan 2, 2026 | Service disruptions in the EU regionThe disruption has now been resolved. | -17 min | Resolved |
| Dec 16, 2025 | Degraded performanceResolved | 29 min | Resolved |
| Nov 11, 2025 | Service disruptions in the EU regionIncident has been resolved. | 60h 41m | Resolved |
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 Tempo 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 Tempo 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 Tempo 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 Tempo outage in this window ran 15d, against a mean recovery of 1d 16h. If you depend on Tempo 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.