Time to SLA - Delayed Jira Issue Synchronization

Summary

Time to SLA - Delayed Jira Issue Synchronization

We have confirmed that the upstream delivery issues have been fully resolved. The backlog of delayed events has been processed, and our systems are once again synchronizing Jira issue creations and updates in real-time.

• Started

  Apr 8, 2026 · 1:57 PM

• Resolved

  Apr 9, 2026 · 8:17 AM

• Duration

  18h 20m

• Severity

  Minor

• ◆

  Identified

  Apr 8 · 1:57 PM Appfire

  We are currently experiencing degraded performance regarding the synchronization of Jira issues. You may notice delays of up to 20 minutes between an action occurring in Jira (such as creating or updating an issue) and that change reflecting in our system. Impact Summary: What is affected: Real-time synchronization of Jira issues. What is NOT affected: No data is being lost. All events are safely queued and will be processed as soon as they are delivered to our system. Who is affected: This is currently impacting all customers utilizing our app, particularly those hosted in the EU and DE regions. Root Cause: This delay is stemming from an ongoing upstream degradation with Atlassian's webhook delivery systems. We are actively monitoring Atlassian's status and are in direct contact with their developer support team to expedite a resolution.

• ◉

  Monitoring

  Apr 8 · 5:21 PM Appfire

  We are seeing event processing times start to return to normal, though it may take a bit more time for the backlog to fully clear. We are closely monitoring delivery rates and will mark this incident as resolved once we confirm all events are consistently arriving without delay.

• ✓

  Resolved

  Apr 9 · 8:17 AM Appfire

  We have confirmed that the upstream delivery issues have been fully resolved. The backlog of delayed events has been processed, and our systems are once again synchronizing Jira issue creations and updates in real-time.