Fix Uptime Reporting for Recovering Incidents

We've fixed a bug that was affecting uptime reporting for incidents published directly to a "Recovering" status.

What was the issue?

When an incident was published directly as "Recovering" (rather than progressing through "Investigating" → "Recovering"), the system wasn't automatically creating the required uptime impact record. This meant these incidents weren't being included in your uptime calculations and reports.

What we've done

We've deployed a fix that ensures all new incidents published directly to "Recovering" will now correctly record their uptime impact.

For historical data, we've backfilled the missing uptime impact records for all affected incidents published since November 14, 2023. These have been recorded with a zero-second duration (began and ended at the same moment), ensuring they appear in your uptime reports without artificially inflating your downtime.

Do you need to do anything?

No action is required. The fix is live and your historical data has been corrected automatically.

If you have any questions or notice any issues with your uptime reports, please don't hesitate to reach out to our support team.