Looking for an update now? Check the current status, or follow Deviniti Cloud Apps for future changes.
100%of 36 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
100%
29
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
7 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
Issue with visibility of templates during work item creation
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been implemented, and we will continue to monitor the issue to ensure it has been fully resolved.
investigating
The issue has been identified.
The behavior observed is an empty list of the templates in the drop-down field on the Issue Templates panel. It is occurring on the native Create screen and the Create from template button.
We’re investigating the source in cooperation with the Atlassian team.
June 2026
Performance issues related to templates selection
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
Atlassian has released a fix for the issue. We have completed our validation and confirmed that full Issue Templates functionality has been restored.
We will continue to monitor the situation and provide further updates if necessary.
identified
We have received confirmation that the Atlassian development team is actively working on a resolution. A fix is expected to be deployed today. We will provide another update once the issue is resolved and services are fully restored.
identified
We have released a hotfix with a workaround (v10.38.0) that should restore Issue Templates functionality.
The template list should now be available; however, the following limitations apply:
- Filtering will not work when the template name differs from the summary.
- The project-specific template list may include issues that should not be available for that project. Availability will be validated only during the apply step.
- The same limitation applies to the availability of users, groups,...
identified
The issue has been identified on the Atlassian side. Atlassian support team informed us that the problem appears to be related to how JQL queries are processed. They have also confirmed that the proper internal development team has been escalated, and they are actively working on the resolution.
investigating
The issue affects template selection during issue creation and other template-related functions, including Apply Template. We have identified the root cause and escalated the issue to Atlassian, as it is caused by a failure of the underlying REST API endpoint. We will provide further updates as they become available.
May 2026
Degraded Performance: Delays in Plugins due to delays in Forge triggers
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are aware that Atlassian is currently experiencing delays with automation triggers, which may also affect our applications. According to Atlassian, their Automation service is the most impacted at this time.
We are monitoring the situation closely and will provide updates as more information becomes available.
You can follow Atlassian's own incident thread here:
https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7
monitoring
Atlassian has updated their statuspage informing about Delay in Jira Webhook Delivery: https://developer.status.atlassian.com/incidents/239w0k720tn3
monitoring
Although Atlassian has closed the incident on their end and marked it as resolved, we are still observing delays in the delivery of Forge trigger-related events.
We have escalated the issue and are actively investigating. We will continue to provide updates here as the situation develops.
monitoring
Status of the source incident can be followed on Atlassian statuspage: https://developer.status.atlassian.com/incidents/m54l7lhqs6cp
monitoring
Atlassian has confirmed that rate limits have been adjusted. However, a significant backlog of 1M+ messages accumulated during the rate limiting period. As the queue processes in order, new events are queued behind the existing backlog - delivery times will improve progressively as the queue drains.
Atlassian is actively monitoring the situation and expects full normalization within the next few hours as the queue count is steadily decreasing.
We are continuing to work closely with Atlassia...
identified
We are continuing to work on a fix for this issue.
identified
We have identified an issue where Atlassian Forge triggers are experiencing significant processing delays. This directly affects data sync within our apps, causing latencies of several to over fifteen minutes.
Our team is in contact with Atlassian support to expedite a resolution. We will provide further updates as they become available.
Degraded Performance: Delays in Plugins due to Atlassian Service Outage
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are seeing significant performance improvements across our apps. New tickets and synchronizations are processing normally, suggesting a minimal event backlog. We will continue to monitor the situation while Atlassian completes their final event replays.
monitoring
Atlassian has confirmed an ongoing incident affecting their core services. This is currently impacting the functionality of the following applications: Extension for JSM, Issue Templates for Jira and Entra ID (Azure AD) Attributes Sync for Jira
You can track Atlassian’s official progress and updates here: https://jira-service-management.status.atlassian.com/incidents/rkzzynzrlmc6
We are monitoring the situation closely and will provide updates as soon as the services are restored.
April 2026
Delays in Jira webhook delivery
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Atlassian has deployed a fix to address the intermittent delays in Jira webhook delivery. The impact on our applications appears to have decreased. We are actively monitoring the situation and will confirm full recovery once it is verified.
We will provide a further update as soon as more information is available.
monitoring
We are continuing to monitor for any further issues.
monitoring
We started observing degraded performance of our application.
While using our plugin, you may experience delays. This issue is related to delays in Jira webhook delivery.
Atlassian has identified the root cause on their side and is currently deploying a fix - https://jira-software.status.atlassian.com/
Extension for JSM - degraded performance and delay
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have received confirmation from Atlassian that the underlying issue has been fully mitigated. Our applications are being monitored and are returning to normal operation. We will continue to observe system behavior and provide a final update once everything is fully confirmed on our end.
If you are still experiencing any issues, please reach out to our support team.
monitoring
We have confirmed that the root cause of the delays is an ongoing incident on Atlassian's side regarding Forge triggers, specifically affecting issue-created and issue-updated events. Atlassian's team is currently working on a resolution.
We are beginning to see signs of improvement, and we expect that affected instances will be restored gradually. We are monitoring the situation closely and will provide further updates as the recovery progresses.
investigating
We are currently experiencing significant delays in receiving ticket creation events from Atlassian. As a result, newly created requests and issues may temporarily display incomplete data in app panels.
We have escalated this issue to Atlassian and are actively monitoring the situation.
Issue templates for Jira Cloud - degraded performance and delay
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have received confirmation from Atlassian that the underlying issue has been fully mitigated. Our applications are being monitored and are returning to normal operation. We will continue to observe system behavior and provide a final update once everything is fully confirmed on our end.
If you are still experiencing any issues, please reach out to our support team.
monitoring
We have confirmed that the degraded performance is linked to an ongoing Atlassian incident affecting Forge triggers, specifically issue-created and issue-updated events. Atlassian is currently working on a resolution.
We are seeing early signs of improvement, and we expect service to be restored gradually across all instances. We will continue to monitor the situation closely until the performance of templates and reports returns to normal.
investigating
We started observing degraded performance of our application. A significant delay in creating issues/structures from templates could occur. This behavior could also affect the creation of reports.
This behavior has been reported and escalated to the Atlassian support team.
