Doodle incident

Doodle.com service interruption.

Critical Resolved View vendor source →

Doodle experienced a critical incident on March 2, 2022 affecting Doodle Web and Apps, lasting 1d 6h. The incident has been resolved; the full update timeline is below.

Started
Mar 02, 2022, 08:46 AM UTC
Resolved
Mar 03, 2022, 03:29 PM UTC
Duration
1d 6h
Detected by Pingoru
Mar 02, 2022, 08:46 AM UTC

Affected components

Doodle Web and Apps

Update timeline

  1. investigating Mar 02, 2022, 08:46 AM UTC

    Some of our users are currently experiencing performance issues and errors while using Doodle. We are working to resume normal service as quickly as possible.

  2. investigating Mar 02, 2022, 09:50 AM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 02, 2022, 01:15 PM UTC

    We are continuing to investigate this issue, and post an update here soon.

  4. investigating Mar 02, 2022, 03:20 PM UTC

    We are continuing to investigate the problems currently being experienced by our users, and we will soon post further updates on this here.

  5. investigating Mar 02, 2022, 06:09 PM UTC

    We are continuing to investigate the problems currently being experienced by our users. We are working to resume normal service as quickly as possible, and do apologize for the inconvenience.

  6. investigating Mar 02, 2022, 08:35 PM UTC

    We are still investigating the problems currently being experienced by our users. We are working to resume normal service as quickly as possible, and do apologize for the inconvenience.

  7. investigating Mar 03, 2022, 08:19 AM UTC

    We are still investigating the problems currently being experienced by our users. We are working to resume normal service as quickly as possible, and do apologize for the inconvenience.

  8. identified Mar 03, 2022, 08:50 AM UTC

    The issue has been identified, and we are working hard to implement a fix. We will post further updates here soon. Once again, we thank you for your continued patience.

  9. monitoring Mar 03, 2022, 12:10 PM UTC

    A fix has been implemented and we are monitoring the results.

  10. resolved Mar 03, 2022, 03:29 PM UTC

    This incident has been resolved.