Appfire JMWE Outage History
Appfire JMWE is up right nowPingoru has recorded 10 incidents for Appfire JMWE: 10 in the last 12 months and 2 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 3 | 91 of 720 (13%) |
| May 2026 | 1 | 1 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 4 of 720 (1%) |
| October 2026 | 1 | 3 of 511 (1%) |
Incidents, newest first
Major October 8, 2026 BigPicture PPM & Strategic Portfolio Management for Jira 2h 34m
Started Oct 08, 2026, 06:34 AM UTC· resolved Oct 08, 2026, 09:09 AM UTC
- investigating Oct 08, 2026, 06:34 AM UTC
Update - Experiencing Degraded performance. We are continuing to investigate.
- investigating Oct 08, 2026, 07:26 AM UTC
Investigations are currently underway, and we will post updates as they become available.
- monitoring Oct 08, 2026, 08:35 AM UTC
The incident has been resolved. We'll continue to monitor closely to confirm stability and provide an update as soon as more information becomes available.
- resolved Oct 08, 2026, 09:09 AM UTC
The incident has been resolved.
Major September 22, 2026 TFS4JIRA Cloud Synchronizer 3h 45m
Started Sep 22, 2026, 11:16 AM UTC· resolved Sep 22, 2026, 03:02 PM UTC
- investigating Sep 22, 2026, 11:16 AM UTC
Customer Impact: The Synchronizer UI is unavailable for most customers. Existing synchronizations remain unaffected and continue to work normally.
Major May 12, 2026 Time to SLA: partial outage in Ohio region 1h 12m
Started May 12, 2026, 10:52 AM UTC· resolved May 12, 2026, 12:04 PM UTC
- identified May 12, 2026, 10:52 AM UTC
During the deployment of the new version, a problem with app packages a version mismatch caused by CI/CD pipeline caused failure. Team identified the problem and is fixing the problem.
- resolved May 12, 2026, 12:04 PM UTC
This incident has been resolved. App is functioning in Ohio region correctly again.
Notice April 25, 2026 Rich Filters migration to Forge 2d 23h
Started Apr 25, 2026, 08:47 AM UTC· resolved Apr 28, 2026, 08:19 AM UTC
- monitoring Apr 25, 2026, 08:47 AM UTC
Rich Filters for Jira Dashboards is moving to Atlassian's Forge platform over several few days. The app is expected to work normally throughout this period. However, a very small number of customers with strict firewall settings reported outages due to the new application domain being blocked. If your organization uses a network security solution, you may need to allowlist *.atlassian-dev.net to maintain access. Please check our documentation for details: https://support.appfire.com/space/RFCDOC/3171189121 You can also reach out to support at: https://support.appfire.com/page/support
- monitoring Apr 27, 2026, 08:30 AM UTC
The migration to Forge has been completed. We will continue to monitor the application closely to confirm stability.
- resolved Apr 28, 2026, 08:19 AM UTC
The migration to Forge is complete, and the app is operating normally for all customers.
Major April 21, 2026 Comala Document Management - Degraded Performance 1h 10m
Started Apr 21, 2026, 04:15 PM UTC· resolved Apr 21, 2026, 05:25 PM UTC
- investigating Apr 21, 2026, 04:15 PM UTC
We are currently investigating an increase in latency and intermittent errors within Comala Document Management. This is due to a sudden surge in database requests that has exceeded our current autoscaling thresholds. Our engineering team is actively working to scale our infrastructure manually to stabilize performance.
- monitoring Apr 21, 2026, 05:12 PM UTC
Performance has stabilized, and error rates have returned to normal levels. We are monitoring to ensure the app remains stable as we investigate the long-term resolution for this traffic pattern.
- resolved Apr 21, 2026, 05:25 PM UTC
This incident has been resolved.
Minor April 8, 2026 Time to SLA - Delayed Jira Issue Synchronization 18h 20m
Started Apr 08, 2026, 01:57 PM UTC· resolved Apr 09, 2026, 08:17 AM UTC
- identified Apr 08, 2026, 01:57 PM UTC
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 08, 2026, 05:21 PM UTC
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 09, 2026, 08:17 AM UTC
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.
Major February 6, 2026 Time to SLA – Partial Outage due to Forge Scheduled Triggers 40m
Started Feb 06, 2026, 11:01 AM UTC· resolved Feb 06, 2026, 11:42 AM UTC
- investigating Feb 06, 2026, 11:01 AM UTC
Time to SLA is currently experiencing a partial outage caused by an issue with Forge scheduled triggers. We are actively monitoring the situation and are awaiting a fix from the Forge platform team. https://developer.status.atlassian.com/incidents/rlrntm2fw82b
- identified Feb 06, 2026, 11:01 AM UTC
The issue has been identified and a fix is being implemented by Forge platform.
- monitoring Feb 06, 2026, 11:27 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 06, 2026, 11:42 AM UTC
This incident has been resolved. Time to SLA and the Forge platform are now operating normally.
Major January 9, 2026 Time to SLA: Degraded performance 56d 3h
Started Jan 09, 2026, 10:14 AM UTC· resolved Mar 06, 2026, 02:04 PM UTC
- identified Jan 09, 2026, 10:14 AM UTC
Time to SLA is currently experiencing degraded performance caused by elevated API rate limiting from Jira platform. We are in contact with Atlassian to understand the root cause of rate limiting and mitigate the problem.
- monitoring Jan 13, 2026, 01:01 PM UTC
Atlassian has provided a fix for API rate limiting from Jira platform. We are continuing our talks with Atlassian and monitoring the systems.
- resolved Mar 06, 2026, 02:04 PM UTC
After an extended observation period, we have confirmed that the implemented changes have successfully mitigated the issue. Performance remains stable, and the incident is now closed.
Notice November 24, 2025 Temporary interruption of Scheduled actions' execution –
Started Nov 24, 2025, 12:00 PM UTC· resolved Nov 24, 2025, 12:00 PM UTC
- resolved Dec 01, 2025, 09:52 AM UTC
An issue in JMWE’s Scheduled Actions runner prevented some scheduled actions from triggering as intended. This incident occurred between Monday 12:00 UTC and Tuesday 19:00 UTC. Appfire team identified and resolved the root cause, restored normal functionality, and reran affected scheduled actions; however, as a result some executions may have occurred with delays or reduced frequency. We recommend that customers review their scheduled actions and manually rerun any that did not execute as intended.
Major November 19, 2025 TFS4JIRA for Azure DevOps: Partial downtime 3h 10m
Started Nov 19, 2025, 11:32 AM UTC· resolved Nov 19, 2025, 02:42 PM UTC
- identified Nov 19, 2025, 11:32 AM UTC
Dear Customers, TFS4JIRA for Azure DevOps user interface is currently not operational. Our team has identified the issue and is actively working to resolve it as quickly as possible. We will provide updates on the status page as we make progress and notify you once the service is fully operational again. Impact: - User Interface Access is unavailable We apologize for the disruption and appreciate your patience. If you have any questions or need further clarification, please feel free to reach out to our support team—we are here to assist you. Thank you for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team
- monitoring Nov 19, 2025, 12:55 PM UTC
Dear customer, We are pleased to inform you that TFS4JIRA is now fully operational. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding. Our team is continuing to monitor the system closely. We will provide further updates as needed. If you have any questions or require assistance, please don’t hesitate to reach out to our support team—we’re here to help. Thank you for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team
- resolved Nov 19, 2025, 02:42 PM UTC
Dear Users, We are pleased to inform you that TFS4JIRA for Azure DevOps is now fully operational. Key Information: - The User Interface is now fully accessible, and all functions have returned to normal. If you have any questions or concerns, please feel free to reach out to our support team. We apologize once again for any inconvenience caused during the downtime and appreciate your patience and understanding. Thank you, and have a great day! Best regards, The TFS4JIRA Team