Starmind incident

Database overload from cronjobs

Critical Resolved View vendor source →

Starmind experienced a critical incident on January 24, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jan 24, 2025, 01:30 AM UTC
Resolved
Jan 24, 2025, 01:30 AM UTC
Duration
—
Detected by Pingoru
Jan 24, 2025, 01:30 AM UTC

Update timeline

  1. resolved Jan 27, 2025, 09:19 AM UTC

    We run multiple overnight jobs to insure the proper functioning of our service. Those jobs overlapped during the night creating too much load on our database. We took measures so that this should not be the case in the future. This affected our european customes.