Some users on affected Tempo instances were unable to access the service and received "403 The app is not installed on this instance" errors, while other users on the same instances could access it normally. The issue affected Timesheets, Planner, and Cost Tracker components for 19.3 hours. Atlassian identified and fixed the root cause related to automation events, restoring access to affected instances.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
We are still working with Atlassian on identifying the root cause for this issue.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with