Files incident

Performance Degradation and/or High Error Rates

Major Resolved View vendor source →

Files experienced a major incident on June 30, 2023 affecting Background Jobs, including Sync and Webhooks, lasting 1h 34m. The incident has been resolved; the full update timeline is below.

Started
Jun 30, 2023, 11:02 PM UTC
Resolved
Jul 01, 2023, 12:37 AM UTC
Duration
1h 34m
Detected by Pingoru
Jun 30, 2023, 11:02 PM UTC

Affected components

Background Jobs, including Sync and Webhooks

Update timeline

  1. investigating Jun 30, 2023, 11:02 PM UTC

    We are investigating a major performance degradation and/or elevated error rates that is affecting all Files.com core and auxiliary services in all regions.

  2. investigating Jul 01, 2023, 12:10 AM UTC

    We are investigating reports of delays to batch and scheduled operations, including some moves, copies, and deletes. This situation should not affect real-time operations such as FTP, SFTP, AS2, and other operations where Files.com acts as a server.

  3. resolved Jul 01, 2023, 12:37 AM UTC

    All services have been restored and are operating normally. We have resolved a situation causing slight error rates and delays to batch and scheduled operations, including moves, copies, and batch file deletion operations. Operations were delayed beginning at 10:00 a.m. PST and ending by 5:30 p.m. PST. All operations did successfully complete despite delays. Preview jobs and some sync jobs were affected for less than 20 minutes during this timeframe. This situation impacted a small proportion of customers. This situation was only a delay of scheduled and batch processing and did not affect real-time operations such as FTP, SFTP, AS2, and other operations where Files.com acts as a server. We will follow up with an Incident Report within ten (10) business days including the root cause and steps taken to address the root cause. If you need additional support, please do not hesitate to contact our Customer Support team by email or phone. Thanks for your support while we resolved this issue.