Ouriginal incident

Degraded report generation

Critical Resolved View vendor source →

Ouriginal experienced a critical incident on November 30, 2022 affecting Report Processing, lasting 2d. The incident has been resolved; the full update timeline is below.

Started
Nov 30, 2022, 06:30 AM UTC
Resolved
Dec 02, 2022, 07:13 AM UTC
Duration
2d
Detected by Pingoru
Nov 30, 2022, 06:30 AM UTC

Affected components

Report Processing

Update timeline

  1. investigating Nov 30, 2022, 06:30 AM UTC

    We are currently investigating this issue.

  2. investigating Nov 30, 2022, 07:34 AM UTC

    We are continuing to investigate this issue.

  3. identified Nov 30, 2022, 08:08 AM UTC

    The issue has been identified and we are working on a solution. The current estimate is that this will take 3+ hours to solve. All documents sent in are being queued and will get a report once the incident is over. Next update in 1 hour.

  4. identified Nov 30, 2022, 09:09 AM UTC

    The issue has been identified and we are working on a solution. The current estimate is that this will take 2+ hours to solve. All documents sent in are being queued and will get a report once the incident is over. Next update in 1 hour.

  5. identified Nov 30, 2022, 10:08 AM UTC

    The issue has been identified and we are working on a solution. The current estimate is that this will take 2 hours to solve. All documents sent in are being queued and will get a report once the incident is over. Next update in 1 hour.

  6. identified Nov 30, 2022, 11:09 AM UTC

    The issue has been identified and we are working on a solution. The current estimate is that this will take 1 hour to solve. All documents sent in are being queued and will get a report once the incident is over. Next update in 1 hour.

  7. identified Nov 30, 2022, 12:12 PM UTC

    The issue has been identified and we are working on a solution. The current estimate is that this will take less than 1 hour to solve. All documents sent in are being queued and will get a report once the incident is over. Next update in 1 hour.

  8. monitoring Nov 30, 2022, 12:48 PM UTC

    A fix has been implemented and we are monitoring the results. We are dealing with the backlog of sent in documents and will generate the reports throughout the day.

  9. monitoring Dec 01, 2022, 07:43 AM UTC

    We are continuing to monitor for further issues while working on clearing the backlog of sent in documents. The backlog will be dealt with throughout the day.

  10. resolved Dec 02, 2022, 07:13 AM UTC

    This incident is now resolved. The backlog has been handled and system is working as intended.

  11. postmortem Jan 10, 2023, 01:51 PM UTC

    This has been an isolated EU incident, our US environment was **NOT** affected. **Course of events** Due to a temporary error in the database no reports were generated. When it was detected, the error was corrected. All reports were saved in a queue and ‌analyzed as soon as the system was running again. **How do we prevent this from happening again?** We have extended our database monitoring. ‌ **How does this affect your organization?** There are no immediate actions you need to take, since we are taking measures to minimize the inconvenience for all customers. ‌‌ We apologize for the inconvenience this may have caused you. **Yours sincerely,** **Team Ouriginal by Turnitin**