7pace Timetracker had 9 outages in the last 2 years totaling 2831h 27m of downtime — averaging 0.4 incidents per month.
There were 9 7pace Timetracker outages since April 19, 2025 totaling 2831h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.
According to our monitoring system this service has become unresponsive.
Our monitoring system reported that this service is back to normal operation.
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