---
title: "Delayed recoveries and false alerts (Nov 6–8)"
description: "Resolved · affects Alerting Engine · Nov 6, 2026"
base_url: "https://status.openstatus.dev"
canonical: "https://status.openstatus.dev/events/report/3869"
homepage_url: "https://openstatus.dev"
contact_url: "mailto:ping@openstatus.dev"
time_zone: "UTC"
---

# Delayed recoveries and false alerts (Nov 6–8)

[Status](/.md) › [Events](/events.md) › Delayed recoveries and false alerts (Nov 6–8)

Nov 6, 2026 · 2 days ago · affects: Alerting Engine · 1 minute

## Updates

### + Resolved — Nov 6, 8:00 PM

affects: Alerting Engine (operational)

Starting Nov 6 around 20:00 UTC, an internal database our check scheduler relies on stopped updating after its disk filled up. As a result, some monitors failed to record recoveries — appearing degraded or down even though checks were passing — and sent repeated degraded/recovered notifications. Monitors created during this window also weren't checked. We expanded storage and rebuilt the database on Nov 8 at 12:55 UTC; all monitors have recovered and we're adding safeguards to prevent this from happening silently again.