11:32 UTC: Database migration caused locks on critical tables, leading to temporary API unavailability.
11:39 UTC: Database locks were removed, and check scheduling began to recover.
Our public API was partially unavailable.
Checks were not scheduled when the locks were effective.
Delayed checks were eventually processed across all regions.
Some high-frequency checks (intervals ≤ 5 minutes) may have skipped a check run during the incident window.
The issue stemmed from a database migration that inadvertently locked critical tables, impacting API and scheduling functionality.
Once the database locks were removed, system recovery began immediately, with checks processing resuming across all regions.
We are reviewing our database migration procedures to minimize locking risks and implementing additional safeguards to ensure API and check scheduling resilience during similar operations.
Feel free to reach out to support if you have any questions. We apologize for the inconvenience and appreciate your understanding as we work to improve our systems.