All Systems Operational

Uptime over the past 90 days. View historical uptime.
Extension for JSM Cloud Operational
90 days ago
100.0 % uptime
Today
Extension for JSM Operational
90 days ago
100.0 % uptime
Today
Issue Templates Cloud Operational
90 days ago
100.0 % uptime
Today
Issue Templates Operational
90 days ago
100.0 % uptime
Today
Requirements & Test Management for Jira Cloud Operational
90 days ago
100.0 % uptime
Today
Requirements & Test Management for Jira Cloud Operational
90 days ago
100.0 % uptime
Today
Dynamic Forms for Jira Cloud Operational
90 days ago
100.0 % uptime
Today
Dynamic Forms for Jira Cloud Operational
90 days ago
100.0 % uptime
Today
Queues for JSM Cloud Operational
90 days ago
100.0 % uptime
Today
Queues for JSM Operational
90 days ago
100.0 % uptime
Today
My Requests Extension for JSM Cloud Operational
90 days ago
100.0 % uptime
Today
My Requests Extension for JSM Cloud Operational
90 days ago
100.0 % uptime
Today
Entra ID (Azure AD) Attributes Sync for Jira Operational
90 days ago
100.0 % uptime
Today
Azure AD Attributes Sync for Jira Operational
90 days ago
100.0 % uptime
Today
Actions for JSM Cloud Operational
90 days ago
100.0 % uptime
Today
Actions for JSM Operational
90 days ago
100.0 % uptime
Today
Issue Sync Pro Operational
90 days ago
100.0 % uptime
Today
Issue Sync Pro Operational
90 days ago
100.0 % uptime
Today
Theme Extension for JSM Cloud Operational
90 days ago
100.0 % uptime
Today
Theme Extension for JSM Cloud Operational
90 days ago
100.0 % uptime
Today
SLA Time Management Operational
90 days ago
100.0 % uptime
Today
SLA Time Management Operational
90 days ago
100.0 % uptime
Today
AI Ticket Assistant Operational
90 days ago
100.0 % uptime
Today
AI Ticket Assistant Operational
90 days ago
100.0 % uptime
Today
Workflow Building Blocks for Jira Operational
90 days ago
100.0 % uptime
Today
Workflow Building Blocks for Jira Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

May 23, 2026

No incidents reported today.

May 22, 2026

No incidents reported.

May 21, 2026

No incidents reported.

May 20, 2026

No incidents reported.

May 19, 2026

No incidents reported.

May 18, 2026

No incidents reported.

May 17, 2026

No incidents reported.

May 16, 2026

No incidents reported.

May 15, 2026

No incidents reported.

May 14, 2026

No incidents reported.

May 13, 2026
Degraded Performance: Delays in Plugins due to delays in Forge triggers
Resolved - The situation has stabilized and full operational status has been restored. All systems are functioning normally. We apologize for any inconvenience caused and thank you for your patience.
May 13, 12:52 CEST
Update - 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
May 13, 09:57 CEST
Update - Atlassian has updated their statuspage informing about Delay in Jira Webhook Delivery: https://developer.status.atlassian.com/incidents/239w0k720tn3
May 12, 16:17 CEST
Update - 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.
May 12, 09:00 CEST
Update - Status of the source incident can be followed on Atlassian statuspage: https://developer.status.atlassian.com/incidents/m54l7lhqs6cp
May 11, 16:49 CEST
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 Atlassian to restore full service stability as quickly as possible.
May 11, 14:40 CEST
Update - We are continuing to work on a fix for this issue.
May 11, 13:31 CEST
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.
May 11, 13:25 CEST
May 12, 2026
May 11, 2026
May 10, 2026

No incidents reported.

May 9, 2026
Degraded Performance: Delays in Plugins due to Atlassian Service Outage
Resolved - All systems are fully operational. This incident has been resolved on Atlassian's end, and our applications are back to normal.
May 9, 10:04 CEST
Update - 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.
May 8, 14:08 CEST
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.
May 8, 10:56 CEST
← Incident History Powered by Atlassian Statuspage