Is Tempo Down Right Now? Check if there is a current outage ongoing.

The issue has been identified. An update to the Tempo panel is being rolled out by Atlassian and the problem should resolve once the rollout is complete.

We have reports from customers that are missing the Tempo panel on the Jira issue view. We are investigating the issue.

The suggestion service in the EU region is currently disrupted. We are investigating the cause and working to restore service.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

We have identified a bottleneck in the system that is causing loss of access or data inconsistency in worklogs and issues between Tempo and Jira and are working on the fastest resolution.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

We have identified a bottleneck in the system that is causing loss of access or data inconsistency in worklogs and issues between Tempo and Jira and are working on the fastest resolution.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have received report that some customers are unable to access Tempo apps. We are investigating.

This incident has been resolved.

Changes to some underlying infrastructure is now improving throughout. The underlying issue appears to have been resolved but we are continuing to monitor the situation.

We are continuing to monitor and investigate the issue.

We are currently experiencing slow data sync with Jira. Worklogs created on new Jira issues or newly updated Jira issues might not display correctly until after a delay.

This incident has been resolved.

A fix has been implemented and we are monitoring the results. All systems should be healthy by now.

A fix has been rolled out to our EU environments.

We have identified the issue that caused the outage. A fix is being implemented.

We are currently investigating an ongoing incident in our US and EU clusters.

The bottleneck we identified has been resolved. If you encounter any issues, especially in worklogs around this incident timeframe, please get in touch with our customer support.

The system was scaled, and we're monitoring

We have been processing a large amount of data on the system in the EU region. Our EU customers may experience data inconsistency in worklogs and issues between Tempo and Jira. We identified the bottleneck in the system and working on the fastest resolution.

Following the maintenance in our EU and DE environments we are experiencing delays in synching worklogs to Jira for some customers. We expect the backend systems to catch up within the next few hours.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Tempo for Jira products down in US

Tempo Timesheets and Planner broken in some cases when loading plans without a description in the UI.

Impact: Users who depended on Jira project permissions for worklog access were affected. Users with Tempo team permissions or “own worklogs” permissions were not impacted. Resolution: We have identified the root cause and taken corrective actions to restore expected access behavior.

Our email processing infrastructure has been running behind and causing delays in email notifications. The problem has been solved and the service is now operating as normal.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We're experiencing degraded performance in backend processing. Our team is looking into the isssue.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Tempo is currently experiencing an incident that is impacting system performance, including issues with generating reports, logging hours, and API calls.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

Production incident in EU

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We have identified an issue that was causing problems with page navigation. Our team is working on a fix which will be rolled out shortly.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are experiencing a loss of services on some of Tempo products. We are currently investigating the issue and will give an update.

This incident has been resolved.

We will update the status when the cause is identified.

Although the outage was resolved by itself, we have been investigating the root cause

We observed that some HTTP requests in Connect Apps struggled to reach application servers. It has been resolved already. But, we haven't been able to identify the root cause.

We confirmed our internal DNS service is now operating without disruption and are taking a measure to prevent it in the future.

Between 8:14 AM and 8:26 AM UTC, users experienced increased request latency and, in some cases, failed requests due to a partial outage in our production cluster due to internal DNS resolution failures.

Between 11:45 AM and 12:20 PM UTC, users experienced increased request latency and, in some cases, failed requests due to a partial outage in our production cluster. We are investigating the root cause and working on a permanent fix to prevent future occurrences. Thank you for your patience.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

Tempo / Jira worklog sync problems identified.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Tempo for Jira in US has reduced latency.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Tempo for Jira in US is down.

All the services are now stable

There was a potential DNS network issue from the EU cluster, and now it's recovered. We continue to monitor our infrastructure.

In the EU region, some customers may experience outage in both public API and Connect App. We're currently troubleshooting.

We identified a partial outage in our EU Kubernetes cluster upon a rollout. For about 15 minutes, some public API HTTP endpoints and access from the Connect App(s) were unresponsive due to resource depletion. We apologize for any impact on our customers. Please reach out to our customer support for assistance.

This incident has been resolved.

Tempo is aware that Australian users are unable to connect to Tempo products.

This incident has been resolved.

Some Time Tracker users have reported the application stalling and being unresponsive. We are investigating the matter.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Tempo for Jira in Europe is down.

The incident has been resolved Atlassian reports that between ~12:15 UTC and ~ 15:20 UTC Jira Cloud Automation rules and Connect apps impersonating users were failing. We have scaled up the underlying services and confirmed we aren't observing failures anymore. We can also confirm from our end that all services with Degraded Performance are now Operational

We are experiencing issues that is impacting performance and availability.

The incident has been resolved Atlassian reports that between ~12:15 UTC and ~ 15:20 UTC Jira Cloud Automation rules and Connect apps impersonating users were failing. We have scaled up the underlying services and confirmed we aren't observing failures anymore. We can also confirm from our end that all services with Degraded Performance are now Operational

We are continuing to investigate this issue. We have found out that Atlassian has yet to be identified degraded instances as Identified by other customers. We are working to resolve this issue

We're experiencing an elevated level of API errors and are currently looking into the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

Our Slack integration is currently experiencing difficulties. The issue has been identified and a fix will be implemented soon.

The access restoration has been completed.

We are working on fixing a problem with authentication. Any customer that has created new API tokens in the last 24 hours may experience a problem accessing, but we are working on restoring access for everyone. We'll be updating the status when the work is done.

The issue has been identified and a fix is being implemented.

Public API outage

A problem with our Public API routing caused failures for some customers. The issue has been identified and resolved.

We made an update to how we route our Public API calls, but due to a problem the update had to be reverted.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have identified the issue and a fix will be rolled out soon.

We're experiencing high load in our backend systems at the moment. This can cause some delay in data processing while the team investigates the underlying issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are encountering service disruptions across all products, we are investigating.

This incident has been resolved.

A fix has been implemented and we are monitoring the results. There might still be some delayed processing for worklogs that should resolve soon.

We have identified the issue and a fix is being implemented.

We are observing increased latency and delayed worklog processing.

A problem with our Teams service caused elevated error rate for some customers. The problem was identified and fixed.

This incident has been resolved.

Issue has been identified and the performance is back to normal. We are continuing to monitor for some time.

Degraded performance seen and currently investigation in progress.

This incident has been resolved.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

Degraded performance

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Degraded performance

We are currently monitoring this issue.

This incident has been resolved.

Latency has returned to normal in our endpoints, we are monitoring.

We are currently investigating this issue.

This incident has been resolved.

This incident has been resolved.

We are continuing to investigate this issue.

The Tempo Support Portal and the Knowledge Base are inoperable

This incident has been resolved.

We identified an issue where our systems were unable to communicate with Jira instances. This seems to have now been resolved on Atlassian's side.

Unable to reach Jira instances, performance degradation

This incident has been resolved.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

We have implemented a fix and are monitoring the situation.

We are investigating an issue with Access Tokens on our Public API. Customers using the API have reported problems accessing the service.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Degraded performance

This incident has been resolved.

We were seeing increased latency in our communication with Jira API, our endpoints that were calling those APIs were encountering degraded performance. Now that Jira APIs are performing better we are seeing better latency.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Customers are unable to access Tempo's single page application (My Work).

This incident has been resolved.

The team is currently monitoring the situation.

Currently investigating reduced performance on our system.