Is Tempo down?
Last checked 9m agoActive incident: Forge Migration Update
Tempo is reporting a partial outage right now (last checked 9m ago). Some components are affected; others remain operational.
Real-time Tempo status, recent outages, and incident history — pulled directly from Tempo's official status page at https://status.tempo.io every 5 minutes. Pingoru tracks 8 Tempo services and has captured 10 incidents in the last 90 days (97.50% uptime). Get email, Slack, Discord, or webhook alerts the moment Tempo reports a new incident — free for 5 monitors, no credit card.
Active incident 1
-
Timeline · 1 update
- monitoring · Apr 02, 2026, 09:46 PM UTC
Status: Monitoring The 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 planned. The automatic migration to Forge is tentatively scheduled to begin on June 15, 2026. You have the option to do either of the following: • Perform a manual update Review the expected changes (see links below) and assess any impacts to your workflows. If the impact is manageable, we recommend updating manually to control the timing of your instance’s migration. • Wait for automatic update The automatic rollout will occur gradually, so we are unable to confirm the exact date your instance will be updated. It will not be possible to schedule, delay, or opt out once started. After your instance is updated, you will receive an in-app notification confirming the change. You can also verify if your instance has migrated to Forge by checking the app versions: https://tempo-io.atlassian.net/wiki/spaces/DRAFTTIMESHEETS/pages/5679415354/Timesheets+Migration+to+Forge+FAQs#How-to-Check-Your-Current-Version. Breaking changes Most of the migration is seamless, but a few things will change that may affect you, particularly around JQL filters: • JQL filter syntax – issueInternal, Account, Tempo Team, and custom field IDs • Tempo Panels in Jira issue view • Keyboard shortcuts • OAuth app URLs Please review the relevant documentation to prepare for changes that might affect you: • Expected Changes in Timesheets on Forge: https://help.tempo.io/timesheets/latest/expected-changes-in-timesheets-on-forge • Expected Changes in Capacity Planner on Forge: https://help.tempo.io/planner/latest/expected-changes-in-capacity-planner-on-forge • Expected Changes in Financial Manager on Forge: https://help.tempo.io/financialmanager/latest/expected-changes-in-financial-manager-on-forge
Latest: Status: Monitoring The migration of Timesheets, Capacity Planner, and Financial Manager to Forge: https://www.tempo.io/product-news/tempo-moves-to-forge is underway, but the automa…
-
Recent outages & incidents
Past 90 days- Adaptive Planner
Timeline · 3 updates
- investigating · Jul 31, 2026, 04:40 AM UTC
Status: Investigating We're experiencing an elevated level of API errors and are currently looking into the issue. Affected components Adaptive Planner (Full outage)
- monitoring · Jul 31, 2026, 05:39 AM UTC
Status: Monitoring The fix has been implemented. We are currently monitoring the rollout. Affected components Adaptive Planner (Full outage)
- resolved · Jul 31, 2026, 12:30 PM UTC
Status: Resolved The issue has been resolved. Affected components Adaptive Planner (Operational)
Latest: Status: Resolved The issue has been resolved. Affected components Adaptive Planner (Operational)
-
- Tempo for Jira Cloud Help CenterCapacity PlannerTime TrackerJiraTempo for SlackTimesheetsFinancial Manager
Timeline · 4 updates
- investigating · Jun 15, 2026, 01:28 PM UTC
Status: Investigating We're currently investigating a brief outage that caused our systems to be inaccessible. The system is up and running now but users can expect delays in event processing. Affected components Timesheets (Partial outage) Financial Manager (Partial outage) Jira (Partial outage) Tempo for Slack (Partial outage) Tempo for Jira Cloud Help Center (Partial outage) Time Tracker (Partial outage) Capacity Planner (Partial outage)
- monitoring · Jun 15, 2026, 01:31 PM UTC
Status: Monitoring The issue has been identified and fixed. We are currently monitoring. Affected components Financial Manager (Operational) Jira (Operational) Tempo for Slack (Operational) Tempo for Jira Cloud Help Center (Operational) Time Tracker (Operational) Capacity Planner (Operational) Timesheets (Operational)
- monitoring · Jun 15, 2026, 04:19 PM UTC
Status: Monitoring Incident has been resolved. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational) Jira (Operational) Tempo for Slack (Operational) Tempo for Jira Cloud Help Center (Operational) Time Tracker (Operational)
- resolved · Jun 15, 2026, 04:20 PM UTC
Status: Resolved Incident has been resolved. Affected components Jira (Operational) Tempo for Slack (Operational) Tempo for Jira Cloud Help Center (Operational) Time Tracker (Operational) Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)
Latest: Status: Resolved Incident has been resolved. Affected components Jira (Operational) Tempo for Slack (Operational) Tempo for Jira Cloud Help Center (Operational) Time Tracker (Opera…
-
-
Timeline · 2 updates
- investigating · Jun 15, 2026, 01:30 PM UTC
Status: Investigating Status: We are currently investigating issues. Impact: Some users may experience degraded performance.
- resolved · Jun 15, 2026, 04:19 PM UTC
Status: Resolved Incident has been resolved.
Latest: Status: Resolved Incident has been resolved.
-
-
Timeline · 2 updates
- investigating · Jun 09, 2026, 01:46 AM UTC
Status: Investigating Status: We are currently investigating issues. Impact: Some users may experience degraded performance.
- resolved · Jun 09, 2026, 08:49 AM UTC
Status: Resolved We had some delay in event processing during last night, the issue has been resolved.
Latest: Status: Resolved We had some delay in event processing during last night, the issue has been resolved.
-
- Capacity PlannerTimesheetsFinancial Manager
Timeline · 4 updates
- investigating · May 12, 2026, 05:31 AM UTC
Status: Investigating Some users on affected instances are unable to use Tempo, while other users on the same instance are able to. The affected users will see the error `403 The app is not installed on this instance` if they open the browser's network tab and look for the `/rest/api/3/mypermissions` being called. We are investigating. Affected components Financial Manager (Partial outage) Capacity Planner (Partial outage) Timesheets (Partial outage)
- investigating · May 12, 2026, 05:19 PM UTC
Status: Investigating We are still working with Atlassian on identifying the root cause for this issue. Affected components Capacity Planner (Partial outage) Timesheets (Partial outage) Financial Manager (Partial outage)
- identified · May 13, 2026, 09:02 AM UTC
Status: Identified Atlassian reported overnight that they've identified and fixed a problem with automation events. We've confirmed on our side that affected instances should now again be able to access. According to Atlassian status page delays can be expected in processing events that have accumulated during the incident. Affected components Capacity Planner (Degraded performance) Timesheets (Degraded performance) Financial Manager (Degraded performance)
- resolved · May 13, 2026, 09:16 AM UTC
Status: Resolved Our customers are reporting that they're able to access Tempo now. Affected components Financial Manager (Operational) Capacity Planner (Operational) Timesheets (Operational)
Latest: Status: Resolved Our customers are reporting that they're able to access Tempo now. Affected components Financial Manager (Operational) Capacity Planner (Operational) Timesheets (O…
-
See the full Tempo outage history
2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Tempo outage history →Or sign up free to get alerts when Tempo breaks · 10 free monitors · No credit card
- Elevated API Errors ResolvedStarted Jul 31, 2026, 12:30 PM UTC · Resolved Jul 31, 2026, 12:30 PM UTC · —
- Brief outage ResolvedStarted Jun 15, 2026, 04:20 PM UTC · Resolved Jun 15, 2026, 04:20 PM UTC · —
- Degraded performance ResolvedStarted Jun 15, 2026, 04:19 PM UTC · Resolved Jun 15, 2026, 04:19 PM UTC · —
- Degraded performance ResolvedStarted Jun 09, 2026, 08:49 AM UTC · Resolved Jun 09, 2026, 08:49 AM UTC · —
- Some users unable to use Tempo ResolvedStarted May 13, 2026, 09:16 AM UTC · Resolved May 13, 2026, 09:16 AM UTC · —
- Degraded performance ResolvedStarted May 08, 2026, 02:54 PM UTC · Resolved May 08, 2026, 02:54 PM UTC · —