Scribbles incident

Website Delays, Learner Account Login Errors

Major Resolved View vendor source →

Scribbles experienced a major incident on May 26, 2026 affecting Parchment Award - Transcript Services and Parchment Award - Diploma, Certificate, Badge, CLR, lasting 1d 1h. The incident has been resolved; the full update timeline is below.

Started
May 26, 2026, 08:08 PM UTC
Resolved
May 27, 2026, 09:43 PM UTC
Duration
1d 1h
Detected by Pingoru
May 26, 2026, 08:08 PM UTC

Affected components

Parchment Award - Transcript ServicesParchment Award - Diploma, Certificate, Badge, CLR

Update timeline

  1. investigating May 18, 2026, 05:46 PM UTC

    We're investigating reports of users unable to access the website. We'll share an update as soon as we have more information.

  2. investigating May 26, 2026, 08:08 PM UTC

    Our investigation is ongoing. We'll share further updates as more information becomes available.

  3. investigating May 26, 2026, 08:10 PM UTC

    We are continuing to investigate this issue.

  4. investigating May 26, 2026, 09:10 PM UTC

    We are continuing to investigate this issue.

  5. identified May 26, 2026, 09:32 PM UTC

    The issue has been identified and a fix is being implemented.

  6. monitoring May 26, 2026, 09:58 PM UTC

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

  7. monitoring May 27, 2026, 02:01 PM UTC

    Our team is closely monitoring our system for any further issues.

  8. investigating May 27, 2026, 04:00 PM UTC

    We're investigating new reports of learners having trouble accessing their Parchment Learner accounts and website delays. We'll share an update as soon as we have more information.

  9. investigating May 27, 2026, 05:18 PM UTC

    We are continuing to investigate this issue.

  10. investigating May 27, 2026, 06:24 PM UTC

    We are continuing to investigate this issue.

  11. investigating May 27, 2026, 07:42 PM UTC

    We are continuing to investigate this issue.

  12. monitoring May 27, 2026, 08:20 PM UTC

    After scaling infrastructure in our registration suite, and applying fixes in our user directory & our registration suite, we have mitigated the issue. The core issue appears to have been a bug in our user sync that was attempting to sync many times for a single user, which was effectively hammering our login infrastructure and causing the degraded service. We fixed the bug and now only sync once per user.

  13. resolved May 27, 2026, 09:43 PM UTC

    This incident has been resolved.