Appfire Cloud Apps Outage History
13 incidents recorded over the last 365 days, 10 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Appfire Cloud Apps Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 26, 2026 | 7pace Timetracker for Azure DevOpsThe underlying Microsoft Azure service disruption has been resolved, and the affected services have been restored. Therefore, this incident has been marked as Resolved. | 14h 44m | Resolved |
| Oct 8, 2026 | BigPicture PPM & Strategic Portfolio Management for JiraThe incident has been resolved. | 2h 34m | Resolved |
| Sep 22, 2026 | TFS4JIRA Cloud SynchronizerThe Synchronizer UI is unavailable for most customers. Existing synchronizations remain unaffected and continue to work normally. | 3h 39m | Resolved |
| May 12, 2026 | Time to SLA: partial outage in Ohio regionThis incident has been resolved. App is functioning in Ohio region correctly again. | 1h 12m | Resolved |
| Apr 25, 2026 | Rich Filters migration to ForgeThe migration to Forge is complete, and the app is operating normally for all customers. | 71h 31m | Resolved |
| Apr 21, 2026 | Comala Document Management - Degraded PerformanceThis incident has been resolved. | 1h 10m | Resolved |
| Apr 8, 2026 | Time to SLA - Delayed Jira Issue SynchronizationWe 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. | 18h 20m | Resolved |
| Apr 6, 2026 | Connector for Salesforce & Jira - Scheduled MaintenanceThe scheduled maintenance for the Connector for Salesforce & Jira has been successfully completed. All services are now fully operational. Thank you for your patience and support during this maintenance window. If you… | 2h 0m | Scheduled |
| Feb 6, 2026 | Time to SLA – Partial Outage due to Forge Scheduled TriggersThis incident has been resolved. Time to SLA and the Forge platform are now operating normally. | 40 min | Resolved |
| Jan 9, 2026 | Time to SLA: Degraded performanceAfter 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. | 1347h 50m | Resolved |
| Dec 22, 2025 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 45 min | Scheduled |
| Dec 16, 2025 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Nov 19, 2025 | TFS4JIRA for Azure DevOps: Partial downtimeDear 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… | 3h 10m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Appfire Cloud Apps incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Appfire Cloud Apps Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Appfire Cloud Apps acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Appfire Cloud Apps outage in this window ran 56d 3h, against a mean recovery of 4d 16h. If you depend on Appfire Cloud Apps in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.