Mohami outage history

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

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.

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

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

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

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.

The incident has been resolved.

The Synchronizer UI is unavailable for most customers. Existing synchronizations remain unaffected and continue to work normally.

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.

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

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

The migration to Forge has been completed. We will continue to monitor the application closely to confirm stability.

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

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.

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.

This incident has been resolved.

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.

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.

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.

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

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

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

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

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.

Atlassian has provided a fix for API rate limiting from Jira platform. We are continuing our talks with Atlassian and monitoring the systems.

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.

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

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

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

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.

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.

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.

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.

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.

We are continuing on waiting a fix from Atlassian.

The incident resolved by Atlassian.

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

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

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

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.

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

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

This incident has been resolved.

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.

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.

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

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

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

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.

This incident has been resolved.

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

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

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

Dear Customer, Today, TFS4JIRA experienced a temporary downtime that impacted normal operations as follows: - Synchronization Services faced delayed requests when rendering data for approximately 5 minutes. - User Interface Access was partially unavailable for approximately 20 minutes. Our team quickly identified and resolved the issue, and we are pleased to inform you that TFS4JIRA is now fully operational. All synchronization operations have resumed without interruptions, including: - Any initial synchronization processes that started before the outage will continue execution as expected. - The User Interface is now fully accessible, and all functions have returned to normal. We sincerely apologize for any inconvenience this downtime may have caused and truly appreciate your patience and understanding. 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

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.

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.

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.