Starting October 26 at 13:00 UTC, Time to SLA data imports from Jira Cloud failed with HTTP 403 errors, affecting Jira Cloud sites with data residency for approximately 22 hours. The root cause was identified and a fix was deployed on October 28, with affected imports automatically restarted. The incident was fully resolved on October 28 at 16:06 UTC.
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.
This incident has been resolved.
We have deployed a fix for the HTTP 403 errors in Time to SLA data imports on Jira Cloud sites with data residency. Imports for the affected accounts have been restarted and will be picked up by the queue. You don't need to change your API token.
We are monitoring the results.
The issue has been identified and a fix is being implemented.
Since October 26, 13:00 UTC, some imports of Time to SLA data from Jira Cloud have been failing with an HTTP 403 (not authorized) error. We are investigating the cause.
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