Last checked
Project, product, and portfolio management software for Jira.
Experiencing an issue?
Is Tempo down?
Degraded performance
Share your experience to help others stay informed.
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Loading reports… · Last 24 hours
Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
| Start | End | Reports | Status |
|---|
Official status checked
Tempo is experiencing issues
Official provider statusOfficial incident active
Forge Migration Update — 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)
Official provider status0 outage reports in the last 24 hours.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 7h 50m | Yes | Critical | ||
| 2h 48m | Yes | Unknown | ||
| 2h 52m | Yes | Major | ||
| 7h 3m | Yes | Unknown | ||
| 19h 17m | Yes | Major | ||
| 7h 54m | Yes | Major | ||
| 3795h 28mOngoing | Yes | Unknown | ||
| 360h 36m | Yes | Minor |
Share your thoughts about Tempo
Be the first to comment!
Uptimus monitors Tempo through its official status source and normalizes published incidents, maintenance windows and component health into one consistent service status.
This page currently includes 8 monitored components, 26 indexed incidents, 0 maintenance windows and 3 days of known history.
Uptimus is an independent monitoring service and is not affiliated with Tempo. A healthy status does not guarantee that every user, device or region is unaffected.
Get notified when Tempo or one of its monitored components reports a major outage or another critical service disruption. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations. The available history contains 26 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “Elevated API Errors”.
Get notified about degraded performance, partial impact and smaller incidents that do not represent a complete outage. Uptimus currently tracks 8 Tempo components: Jira, Tempo for Slack, Financial Manager, Tempo for Jira Cloud Help Center. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.
Downdetector public pages are led by user reports. Uptimus combines community activity with official provider incidents, maintenance windows and component health when the source publishes them.
| Comparison criteria | Uptimus | Downdetector |
|---|---|---|
| Community outage reports for Tempo |
The current official status of Tempo cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Tempo in the last 24 hours. Last official check: .
| Included |
| Adaptive baseline that separates isolated reports from wider disruption | Included | Included |
|---|
| 24-hour report activity and regional outage view | Included | Included |
|---|
| One workspace for websites, provider status pages, Steam games and Android apps and games | Included | Separate product |
|---|
| Email, push and webhook alerts from the same workspace | Included | Separate product |
|---|
| Official incident updates and status timeline for Tempo | Included | User-report led |
|---|
| Component health and maintenance windows kept separate | Included | Limited on public pages |
|---|
Rate this service
No reviews yet