Deviniti Outage History

The fix has been implemented, and we will continue to monitor the issue to ensure it has been fully resolved.

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.

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 Atlassian to restore full service stability as quickly as possible.

Status of the source incident can be followed on Atlassian statuspage: https://developer.status.atlassian.com/incidents/m54l7lhqs6cp

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.

Atlassian has updated their statuspage informing about Delay in Jira Webhook Delivery: https://developer.status.atlassian.com/incidents/239w0k720tn3

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

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.

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.

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/

We are continuing to monitor for any further issues.

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.

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.

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.

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.

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.

We are currently investigating reports of performance issues and potential outages within Queues for Jira & JSM. This behavior appears to be linked to an ongoing incident at Atlassian affecting their core infrastructure. Our team is monitoring the situation closely and will provide updates as soon as more information becomes available. You can track the status of the underlying Atlassian incident here: https://developer.status.atlassian.com/incidents/r0qnp3j2yzxn

According to our logs, the problem has not reoccurred since 03:00 UTC on 27.02.2026, and the service appears to be operating normally at this time. We will continue monitoring the situation closely to ensure stability.

From our initial analysis, it seems the application became temporarily overloaded, which caused the issue. Restarting the app restored normal operation. We will investigate it further to understand the cause of this issue. At the moment, the application is working normally.

We have just deployed a set of fixes addressing the recently reported bugs. According to our internal tests, these updates should significantly improve the application's stability and performance. Our team is currently monitoring the situation closely to ensure everything is back to normal. Thank you for your patience.

Server-side logs indicate that the issue has been resolved. We are now verifying the fix with our customers. We will provide a final update once we receive confirmation that everything is back to normal.

We have deployed fixes for the majority of the reported issues. Our team is now focused on resolving a few remaining edge cases to ensure full stability. We will provide another update as soon as we have more information.

Most reported issues have been resolved, and the platform is operating normally for the majority of users. We are about to deploy an update restoring scope behavior to its previous state, which will address the remaining reports from a small number of customers. One additional edge case is still being investigated. Our engineering team is actively working on this and coordinating with Support. We will provide another update once it's available.

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

Partial recovery: Access restored for the majority of customers. We have observed significant improvement regarding the access issues for Queues for Jira & JSM. A fix has been implemented, and the majority of our customers can now use the application correctly without any interruption. However, we are aware of remaining edge cases where access may still be unstable for specific instances. We are continuing to work closely with Atlassian to isolate and resolve these residual issues associated with the Forge migration. We will provide another update once we confirm full resolution for all users.

We are currently observing potential service degradation in the EU region, caused by an ongoing issue with our cloud service provider, Heroku. Some users may experience limited functionality or intermittent disruptions. We are closely monitoring the situation. Once Heroku resolves the issue, the affected services on our side are expected to recover automatically. No action is required from users at this time. We will continue to provide updates as the situation evolves. Thank you for your understanding.

You can follow the progress of this issue on the Heroku side here: https://status.heroku.com/incidents/2822

The production version is now deployed, and no issues are expected. All functionalities should be working as usual.