Service Fusion incident

AWS Recovery

Minor Resolved View vendor source →

Service Fusion experienced a minor incident on October 20, 2025 affecting Admin System - admin.servicefusion.com and Worker App and 1 more component, lasting 11h 47m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 11:40 AM UTC
Resolved
Oct 20, 2025, 11:28 PM UTC
Duration
11h 47m
Detected by Pingoru
Oct 20, 2025, 11:40 AM UTC

Affected components

Admin System - admin.servicefusion.comWorker Appvip1, vip2 and other *.totalfsm.com domainsQuickBooks Desktop IntegrationQuickBooks Online IntegrationCustomer Web Portal & Customer AppsAPI (beta)FusionPayServiceCall.aiGPS Fleet Tracking

Update timeline

  1. monitoring Oct 20, 2025, 11:40 AM UTC

    A fix has been implemented to assist in the recovery of AWS issues from the period of 10 /19. We are monitoring the results.

  2. monitoring Oct 20, 2025, 12:48 PM UTC

    We are continuing to monitor as AWS continues the recovery process.

  3. monitoring Oct 20, 2025, 01:56 PM UTC

    We are continuing to monitor as AWS continues the recovery process.

  4. monitoring Oct 20, 2025, 02:56 PM UTC

    We are continuing to monitor as AWS continues the recovery process. We will continue to update as additional information becomes available.

  5. monitoring Oct 20, 2025, 04:20 PM UTC

    We are continuing to monitor as AWS continues the recovery process. We will continue to update as additional information becomes available.

  6. monitoring Oct 20, 2025, 06:28 PM UTC

    We are continuing to monitor as AWS continues the recovery process. We will continue to update as additional information becomes available.

  7. monitoring Oct 20, 2025, 09:41 PM UTC

    AWS has reported improvements in recovery on their end, and we are now seeing Service Fusion systems successfully navigating as expected. While functionality appears stable, our team will continue to actively monitor performance to ensure full resolution and prevent any recurrence.

  8. resolved Oct 20, 2025, 11:28 PM UTC

    This incident has been resolved.