Is Tempo down?

Last checked 1m ago
Current status
Tempo is having a partial outage

2 active incidents: Maintenance: Infrastructure maintenance, Forge Migration Update

Official status page: https://status.tempo.io · Polled every 5 minutes · 8 components tracked

Tempo is reporting a partial outage right now (last checked 1m 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 13 incidents in the last 90 days (98.26% uptime). Get email, Slack, Discord, or webhook alerts the moment Tempo reports a new incident — free for 5 monitors, no credit card.

Users who monitor Tempo also follow these Project Management services: Atlassian Jira Software Trello Asana Incident IQ Notion Shortcut Jira Service Management LaunchDarkly Basecamp View all 6,000+ providers
Tempo uptime 98.26% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Active incident 1

  1. Ongoing ● 72d
    Started Apr 02, 2026, 09:46 PM UTC
    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
  1. Resolved
    Started Jun 09, 2026, 08:49 AM UTC · Resolved Jun 09, 2026, 08:49 AM UTC
    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.

  2. Resolved
    Started May 13, 2026, 09:16 AM UTC · Resolved May 13, 2026, 09:16 AM UTC
    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…

  3. Resolved
    Started May 08, 2026, 02:54 PM UTC · Resolved May 08, 2026, 02:54 PM UTC
    Capacity PlannerTimesheetsFinancial Manager
    Timeline · 4 updates
    • investigating · May 08, 2026, 07:00 AM UTC

      Status: Investigating Status: We are currently investigating issues. Impact: Some users may experience degraded performance.

    • investigating · May 08, 2026, 10:26 AM UTC

      Status: Investigating We are still investigating a partial outage affecting Tempo for Jira Cloud, primarily impacting a subset of customers in the us-east-1 region. AWS Health has reported a severe degradation in the relevant region. Their team is currently investigating our particular issue and we are waiting for an update from them. Affected components Timesheets (Partial outage) Financial Manager (Partial outage) Capacity Planner (Partial outage)

    • monitoring · May 08, 2026, 02:05 PM UTC

      Status: Monitoring Together with AWS Support we were able to restore function to our backend systems that were affected by the outage. AWS continues to have degraded performance in the region, but we are now fully operational again. We will continue to monitor the situation. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

    • resolved · May 08, 2026, 02:54 PM UTC

      Status: Resolved Incident has been resolved. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

    Latest: Status: Resolved Incident has been resolved. Affected components Capacity Planner (Operational) Timesheets (Operational) Financial Manager (Operational)

  4. Resolved 24d 3h
    Started Apr 02, 2026, 09:46 PM UTC · Resolved Apr 27, 2026, 01:30 AM UTC
  5. Resolved
    Started Mar 18, 2026, 02:24 PM UTC · Resolved Mar 18, 2026, 02:24 PM UTC
    Timesheets
    Timeline · 3 updates
    • investigating · Mar 03, 2026, 01:48 PM UTC

      Status: Investigating We are currently experiencing delays in calendar event synchronization for users with Microsoft Outlook (O365) and Google Calendar integrations. Events may not appear in Tempo Timesheets as expected. Our engineering team is actively investigating the issue. We will provide further updates as we learn more. We apologize for the inconvenience. Affected components Timesheets (Degraded performance)

    • investigating · Mar 13, 2026, 08:50 PM UTC

      Status: Investigating We have temporarily remedied the degraded performance by scaling up the system. We continue to investigate the root cause. Affected components Timesheets (Degraded performance)

    • resolved · Mar 18, 2026, 02:24 PM UTC

      Status: Resolved We have identified and addressed the root cause of the delays. The issue is now resolved. Affected components Timesheets (Operational)

    Latest: Status: Resolved We have identified and addressed the root cause of the delays. The issue is now resolved. Affected components Timesheets (Operational)

See the full Tempo outage history

1 more incident 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

Outage history

Past 90 days · 6 incidents View full outage history →