PairSoft incident

PaperSaveCloud Service Interruption Alert

Critical Resolved View vendor source →

PairSoft experienced a critical incident on August 10, 2022 affecting Operations Service (PSLAAS01P) and Operations Service (PSLAAS02P) and 1 more component, lasting 4h 42m. The incident has been resolved; the full update timeline is below.

Started
Aug 10, 2022, 09:19 PM UTC
Resolved
Aug 11, 2022, 02:02 AM UTC
Duration
4h 42m
Detected by Pingoru
Aug 10, 2022, 09:19 PM UTC

Affected components

Operations Service (PSLAAS01P)Operations Service (PSLAAS02P)Operations Service (PSLAAS03P)Operations Service (PSLAAS04P)Operations Service (PSLAAS05P)Operations Service (PSLAAS06P)Operations Service (PSLAAS07P)Operations Service (PSLAAS08P)Operations Service (PSLAAS09P)Operations Service (PSLAAS10P)

Update timeline

  1. investigating Aug 10, 2022, 09:19 PM UTC

    We are experiencing issues with the PaperSaveCloud services. These issues may prevent you from accessing or using parts of your PaperSave application. Our Teams are actively working on the remediation. Please check here periodically for updates. We apologize for any inconvenience.

  2. investigating Aug 10, 2022, 09:56 PM UTC

    We are continuing to investigate this issue.

  3. identified Aug 10, 2022, 11:49 PM UTC

    We are still working on the issue. The issue is rooted in a failure that occurred in one of our network providers. We are working with that provider. We will send another update in 2 hours unless we resolve the issue earlier.

  4. identified Aug 11, 2022, 12:49 AM UTC

    We are still working on the issue. The issue is rooted in a failure that occurred in a networking component managed by one of our infrastructure providers. We are working with that provider. We will send another update in 1 hour unless we resolve the issue earlier. We will share an ETA on a resolution as soon as we know more.

  5. monitoring Aug 11, 2022, 01:11 AM UTC

    The issue has been resolved. We are monitoring for the next hour before officially closing the incident as resolved. We will be investigating the incident and looking for ways to mitigate any future reoccurrence. We apologize for the inconvenience.

  6. resolved Aug 11, 2022, 02:02 AM UTC

    Issue is resolved. We apologize for the downtime you experienced. We will be running a retrospective on this incident to identify ways that we can improve our infrastructure to avoid and or mitigate a future reoccurrence