EasyCron incident

easycron is having some trouble, we're working on a solution

Critical Resolved View vendor source →

EasyCron experienced a critical incident on July 6, 2022 affecting Website and API and 1 more component, lasting 37m. The incident has been resolved; the full update timeline is below.

Started
Jul 06, 2022, 02:01 PM UTC
Resolved
Jul 06, 2022, 02:39 PM UTC
Duration
37m
Detected by Pingoru
Jul 06, 2022, 02:01 PM UTC

Affected components

WebsiteAPIExecutors

Update timeline

  1. investigating Jul 06, 2022, 02:01 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 06, 2022, 02:07 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 06, 2022, 02:23 PM UTC

    A fix has been applied, and the service is back online. We're working on a fix to permanently stabilize the service.

  4. resolved Jul 06, 2022, 02:39 PM UTC

    Service is working during the monitoring of 15 minutes. We're working on a patch to fix the intermittent problem.

  5. postmortem Jul 06, 2022, 03:43 PM UTC

    Cron job triggering processes were wrongly identified as “should be cancelled“ by monitoring component, and then were cancelled. We have removed that monitoring component. Same kind of errors should not happen again in the future.