Appfire Outage History

Started Oct 26, 2026, 02:27 PM UTC· resolved Oct 27, 2026, 05:11 AM UTC

1. investigating Oct 26, 2026, 02:27 PM UTC

   We are investigating an issue affecting 7pace Timetracker in the West Europe region. Some functionality is currently unavailable. We are investigating the issue.

2. identified Oct 26, 2026, 04:59 PM UTC

   We have identified that the issue affecting is related to an underlying Microsoft Azure service disruption. However, some customers may still experience an impact while service recovery completes and will provide further updates as service availability is restored.

3. monitoring Oct 26, 2026, 07:48 PM UTC

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

4. resolved Oct 27, 2026, 05:11 AM UTC

   The underlying Microsoft Azure service disruption has been resolved, and the affected services have been restored. Therefore, this incident has been marked as Resolved.

Read the full incident report →

Started Oct 08, 2026, 06:34 AM UTC· resolved Oct 08, 2026, 09:09 AM UTC

1. investigating Oct 08, 2026, 06:34 AM UTC

   Update - Experiencing Degraded performance. We are continuing to investigate.

2. investigating Oct 08, 2026, 07:26 AM UTC

   Investigations are currently underway, and we will post updates as they become available.

3. 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.

4. resolved Oct 08, 2026, 09:09 AM UTC

   The incident has been resolved.

Read the full incident report →

Started May 12, 2026, 10:52 AM UTC· resolved May 12, 2026, 12:04 PM UTC

1. 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.

2. resolved May 12, 2026, 12:04 PM UTC

   This incident has been resolved. App is functioning in Ohio region correctly again.

Read the full incident report →

Started Apr 25, 2026, 08:47 AM UTC· resolved Apr 28, 2026, 08:19 AM UTC

1. 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

2. 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.

3. resolved Apr 28, 2026, 08:19 AM UTC

   The migration to Forge is complete, and the app is operating normally for all customers.

Read the full incident report →

Started Apr 21, 2026, 04:15 PM UTC· resolved Apr 21, 2026, 05:25 PM UTC

1. 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.

2. 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.

3. resolved Apr 21, 2026, 05:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 08, 2026, 01:57 PM UTC· resolved Apr 09, 2026, 08:17 AM UTC

1. 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.

2. 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.

3. 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.

Read the full incident report →

Started Feb 06, 2026, 11:01 AM UTC· resolved Feb 06, 2026, 11:42 AM UTC

1. 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

2. identified Feb 06, 2026, 11:01 AM UTC

   The issue has been identified and a fix is being implemented by Forge platform.

3. monitoring Feb 06, 2026, 11:27 AM UTC

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

4. resolved Feb 06, 2026, 11:42 AM UTC

   This incident has been resolved. Time to SLA and the Forge platform are now operating normally.

Read the full incident report →

Started Jan 09, 2026, 10:14 AM UTC· resolved Mar 06, 2026, 02:04 PM UTC

1. 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.

2. 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.

3. 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.

Read the full incident report →

Started Nov 19, 2025, 11:32 AM UTC· resolved Nov 19, 2025, 02:42 PM UTC

1. 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

2. 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

3. 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

Read the full incident report →

Started Jul 18, 2025, 03:00 PM UTC· resolved Jul 18, 2025, 03:00 PM UTC

1. resolved Jul 21, 2025, 04:21 PM UTC

   On Friday around 14:57 UTC for about an hour we experienced the incident in the Canned Responses application. The issue was caused by a temporary database outage, which made the app unusable. Everything is now back to normal, we are currently working with a database supplier, so that such a problem does not repeat in the future. We apologize for any inconvenience caused during the downtime and appreciate your patience and understanding.

Read the full incident report →

Started Jul 17, 2025, 10:17 AM UTC· resolved Jul 30, 2025, 08:25 AM UTC

1. investigating Jul 17, 2025, 10:17 AM UTC

   We are currently investigating a problem where several instances are facing problems while trying to get the app properties from Jira REST API. No possible reason has been found, we have been able to reproduce it in one of the test environments we have.

2. identified Jul 17, 2025, 12:50 PM UTC

   The problem seems to be the app user not having the correct permission in several instances. We are trying to find possible solutions as well as actions we can take. A ticket to Atlassian has also been submitted.

3. identified Jul 17, 2025, 05:53 PM UTC

   https://ecosystem.atlassian.net/servicedesk/customer/portal/34/ECOHELP-76209 has been progressed into 'In Progress' status around 4 hours ago, still waiting for further updates.

4. identified Jul 18, 2025, 08:39 AM UTC

   Atlassian approved the problem is caused by the Forge and created a incident of their own. https://developer.status.atlassian.com/incidents/8gwd2x0ql9l3 Waiting for fix from Atlassian.

5. identified Jul 30, 2025, 08:25 AM UTC

   We are continuing on waiting a fix from Atlassian.

6. resolved Jul 30, 2025, 08:25 AM UTC

   The incident resolved by Atlassian.

Read the full incident report →

Started Jun 17, 2025, 09:44 AM UTC· resolved Jun 17, 2025, 12:04 PM UTC

1. identified Jun 17, 2025, 09:44 AM UTC

   Dear Customer, TFS4JIRA is experiencing a partial outage that is affecting normal operations: Synchronization Service is facing an error during synchronization from Jira to Azure. Our team has already identified the issue and is taking immediate action to resolve it. We sincerely apologize for any inconvenience this may cause and appreciate your patience and understanding. 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. Best regards, The TFS4JIRA Team

2. monitoring Jun 17, 2025, 11:47 AM UTC

   Dear Customer, Earlier today, TFS4JIRA experienced a partial outage that affected normal operations. Our team promptly identified the root cause and implemented a fix. We’re happy to confirm that TFS4JIRA is now fully operational, and all synchronization activities have resumed. We are actively monitoring the system to ensure continued stability. We sincerely apologize for any inconvenience caused by this disruption and appreciate your patience and understanding throughout the incident. If you have any questions or require further assistance, please don’t hesitate to contact our support team—we’re here to help. Thank you for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team

3. resolved Jun 17, 2025, 12:04 PM UTC

   Dear Customer, We’re pleased to share that the recent issue impacting TFS4JIRA has been fully resolved, and the system is now operating normally. Earlier today, a partial outage affected synchronization from Jira to Azure DevOps for a subset of our customers. Our engineering team quickly identified the root cause, implemented a fix, and we have since completed the monitoring period to confirm that all services are functioning as expected. We sincerely appreciate your patience and understanding during this incident. If you have any questions or notice any issues, our support team is ready to assist. Thank you again for your continued trust in TFS4JIRA. Best regards, The TFS4JIRA Team

Read the full incident report →

Started May 07, 2025, 09:01 AM UTC· resolved May 07, 2025, 01:23 PM UTC

1. investigating May 07, 2025, 09:01 AM UTC

   Due to an incident on Google Cloud Platform in eu-west3 region Canned Responses Pro users in Germany may be experiencing interruption of service. The team is investigating if the issue can be worked around.

2. identified May 07, 2025, 09:02 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring May 07, 2025, 09:15 AM UTC

   The GCP incident has been resolved, Canned Responses Pro is back to normal function. The team keeps monitoring the situation.

4. resolved May 07, 2025, 01:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 07, 2025, 08:04 AM UTC· resolved May 07, 2025, 11:30 AM UTC

1. investigating May 07, 2025, 08:04 AM UTC

   The TFS4JIRA for Azure DevOps is currently unavailable. Customers will experience issues performing key activities. Current Update: We are aware of the outage affecting the app and are actively investigating the root cause. Our engineering team is working to restore full functionality as quickly as possible. We apologize for the disruption and appreciate your patience. The next update will be provided in 2 hours or sooner.

2. identified May 07, 2025, 08:55 AM UTC

   The TFS4JIRA for Azure DevOps is currently unavailable. Customers will experience issues performing key activities. Current Status: We have identified the root cause of the issue. It is related to an ongoing incident with our cloud provider. We are actively working with them to resolve the problem as quickly as possible. We apologize for the disruption and appreciate your patience. The next update will be provided in 2 hours or sooner.

3. monitoring May 07, 2025, 10:39 AM 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

4. resolved May 07, 2025, 11:30 AM UTC

   Dear Users, We are pleased to inform you that TFS4JIRA for Azure DevOps is now fully operational. Key Information: - No synchronization data has been lost. - All synchronizations resumed automatically. 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

Read the full incident report →

Started Apr 08, 2025, 11:30 AM UTC· resolved Apr 08, 2025, 11:30 AM UTC

1. resolved Apr 10, 2025, 02:14 PM UTC

   On 8th April 2025, Toggl encountered issues due to a gradual rollout of changes by Atlassian, which affected a portion of our customers. Issue has been resolved

Read the full incident report →

Started Mar 11, 2025, 07:32 PM UTC· resolved Mar 11, 2025, 09:06 PM UTC

1. monitoring Mar 11, 2025, 07:32 PM UTC

   Time to SLA app was down in the US region starting from 8 AM EST. The app was restored at 2 PM and we are currently monitoring the app.

2. resolved Mar 11, 2025, 09:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 14, 2025, 12:50 PM UTC· resolved Feb 14, 2025, 04:13 PM UTC

1. monitoring Feb 14, 2025, 12:50 PM UTC

   Dear Customer, Earlier today, TFS4JIRA experienced a temporary downtime that affected normal operations: - Synchronization Services encountered delayed requests when rendering data for approximately 15 minutes. Our team quickly identified the issue and took immediate action to resolve it. We are actively monitoring the system to ensure full stability. We are pleased to inform you that TFS4JIRA is now fully operational, and all synchronization processes have resumed without interruption. Any initial synchronization processes that began before the outage are continuing as expected. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding. 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

2. monitoring Feb 14, 2025, 12:57 PM UTC

   Dear customer, We are pleased to inform you that TFS4JIRA is now fully operational, and all synchronization processes have resumed without interruption. Any initial synchronization processes that began before the outage are continuing as expected. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding. 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

3. resolved Feb 14, 2025, 04:13 PM UTC

   Dear Customer, We are pleased to inform you that TFS4JIRA for Azure DevOps is now fully operational. We apologize once again for any inconvenience this may have caused and appreciate your patience and understanding. 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

Read the full incident report →

Started Feb 11, 2025, 05:58 AM UTC· resolved Feb 11, 2025, 09:35 AM UTC

1. investigating Feb 11, 2025, 05:58 AM UTC

   The Connector for Salesforce & Jira is currently intermittently unavailable. Customers may experience issues performing key activities. Current Update: We are aware of the outage affecting the app and are actively investigating the root cause. Our engineering team is working to restore full functionality as quickly as possible. We apologize for the disruption and appreciate your patience. The next update will be provided in 2 hours or sooner.

2. monitoring Feb 11, 2025, 07:29 AM UTC

   Connector for Salesforce & Jira : Service Restored The service has been restored, and all functionality should now be operating normally. Customers may have experienced intermittent unavailability of the Connector for Salesforce & Jira. Our team is continuing to monitor system performance closely. We are also conducting a detailed investigation to determine the root cause and ensure long-term stability. We will continue monitoring for the next 2 hours, after which we will mark this incident as resolved if no further issues arise. We sincerely apologize for the disruption and appreciate your patience. If you are still experiencing any issues, please reach out to our support team.

3. resolved Feb 11, 2025, 09:35 AM UTC

   Connector for Salesforce & Jira : Incident Resolved The service has remained stable following our monitoring period, and we are now marking this incident as resolved. Our team will continue conducting a detailed review to prevent future occurrences. We sincerely apologize for any disruption this may have caused and appreciate your patience. If you experience any further issues, please reach out to our support team.

Read the full incident report →

Started Jan 09, 2025, 12:07 PM UTC· resolved Jan 09, 2025, 01:16 PM UTC

1. identified Jan 09, 2025, 12:07 PM UTC

   Dear Users, TFS4JIRA for Azure DevOps 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: - Synchronization between Jira and Azure DevOps will not occur during this downtime. - Normal operations will resume once TFS4JIRA is restored. We sincerely apologize for any inconvenience this may cause and thank you for your patience and understanding. Best regards, The TFS4JIRA Team

2. monitoring Jan 09, 2025, 12:39 PM UTC

   Dear Users, We are pleased to inform you that TFS4JIRA for Azure DevOps is now operational, and we are monitoring it. Key Information: - No synchronization data has been lost. - All synchronizations will resume automatically. 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

3. resolved Jan 09, 2025, 01:16 PM UTC

   Dear Users, We are pleased to inform you that TFS4JIRA for Azure DevOps is now fully operational. Key Information: - No synchronization data has been lost. - All synchronizations will resume automatically. 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

Read the full incident report →

Started Dec 19, 2024, 01:00 PM UTC· resolved Dec 19, 2024, 04:32 PM UTC

1. investigating Dec 19, 2024, 01:40 PM UTC

   Navigation within the app is not working correctly (nothing happens after clicking in-app links). The team has identified the root cause of the issue: an unexpected change in the Atlassian Connect Front-end API behavior, which broke the logic behind switching between app views. The team is working on a hotfix.

2. resolved Dec 19, 2024, 04:32 PM UTC

   Our team The issue has now been resolved. The hotfix has been successfully deployed, and navigation within the app is functioning as expected. Please let us know if you encounter any further issues. Thank you for your patience!

Read the full incident report →

Started Dec 19, 2024, 12:35 PM UTC· resolved Dec 20, 2024, 12:55 PM UTC

1. investigating Dec 19, 2024, 12:35 PM UTC

   We are seeing issues with switching between issues/chat in the Chat Dashboard. The team is actively investigating the issue and will provide an update shortly.

2. identified Dec 19, 2024, 12:50 PM UTC

   The team has identified the route cause of the issue - there was an unexpected change in Atlassian Connect JavaScript API behavior, breaking the logic behind switching between chats. The team is working on a hotfix, more updates to follow shortly.

3. monitoring Dec 19, 2024, 02:53 PM UTC

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

4. monitoring Dec 20, 2024, 10:31 AM UTC

   The issue is fully resolved and the app is operational.

5. resolved Dec 20, 2024, 12:55 PM UTC

   This incident has been resolved.

Read the full incident report →