ZapSign incident

AWS Cloud Provider Incident Update

Critical Resolved View vendor source →

ZapSign experienced a critical incident on February 9, 2024 affecting API, lasting 4h 26m. The incident has been resolved; the full update timeline is below.

Started
Feb 09, 2024, 11:53 AM UTC
Resolved
Feb 09, 2024, 04:19 PM UTC
Duration
4h 26m
Detected by Pingoru
Feb 09, 2024, 11:53 AM UTC

Affected components

API

Update timeline

  1. investigating Feb 09, 2024, 11:53 AM UTC

    We encountered an issue with AWS, our cloud provider. The automated backup routine scheduled for 03:00 failed to complete on time, resulting in platform slowdowns. We are actively monitoring and working to restore normal operations within approximately 40 minutes. Additionally, we are deploying another failover replica to mitigate the impact. Thank you for your patience as we resolve this issue.

  2. investigating Feb 09, 2024, 11:53 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 09, 2024, 02:31 PM UTC

    Apologies for the inconvenience. The new estimated time for resolving the issue with AWS is 11:50. We are working to restore normal operations as quickly as possible. Thank you for your patience

  4. investigating Feb 09, 2024, 02:53 PM UTC

    We appreciate your patience as we work to restore normal operations

  5. investigating Feb 09, 2024, 04:16 PM UTC

    We are pleased to announce that the issue with our AWS cloud provider has been resolved. The automated backup routine, which previously caused platform slowdowns, has been successfully addressed. Normal operations have been restored as of 13:15 (Brazil time, UTC-3).

  6. investigating Feb 09, 2024, 04:18 PM UTC

    We are continuing to investigate this issue.

  7. resolved Feb 09, 2024, 04:19 PM UTC

    We appreciate your understanding and patience throughout this incident. If you encounter any further issues, please don't hesitate to contact us. Thank you for your cooperation.