Status: Resolved The issue has been resolved. Affected components
 <ul>
 <li>Adaptive Planner (Operational)</li>
 </ul>

Elevated API Errors

Status: Complete The maintenance has been completed. Affected components
 <ul>
 <li>Adaptive Planner (Operational)</li>
 </ul>

Maintenance: Infrastructure maintenance

Status: Resolved Incident has been resolved. Affected components
 <ul>
 <li>Time Tracker (Operational)</li>
<li>Capacity Planner (Operational)</li>
<li>Timesheets (Operational)</li>
<li>Financial Manager (Operational)</li>
<li>Jira (Operational)</li>
<li>Tempo for Slack (Operational)</li>
<li>Tempo for Jira Cloud Help Center (Operational)</li>
 </ul>

Brief outage

Status: Resolved Incident has been resolved.

Degraded performance

Status: Resolved We had some delay in event processing during last night, the issue has been resolved.

Status: Complete Maintenance has completed Affected components
 <ul>
 <li>Capacity Planner (Under maintenance)</li>
<li>Timesheets (Under maintenance)</li>
<li>Financial Manager (Under maintenance)</li>
 </ul>

Maintenance: Maintenance in the US region

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

Is Tempo down?

Tempo status is UP

Lastest published events

Elevated API Errors

Maintenance: Infrastructure maintenance

Brief outage

Tempo Services, Components and Regions

Recent Tempo events

Elevated API Errors

Maintenance: Infrastructure maintenance

Brief outage

Degraded performance

Degraded performance

Maintenance: Maintenance in the US region