Platform Outage and Ongoing Monitoring Degradation (Monitoring)
Updates
- Identified
We have confirmed that the initial outage was triggered by urgent infrastructure maintenance performed by our hosting provider.
Public status-page availability has been restored. However, our monitoring scheduler did not recover automatically after the server restarted.
As a result, some scheduled monitoring checks, automated incident processing, and alert notifications remain unavailable or delayed.
We are validating a controlled recovery procedure to restore monitoring safely, without allowing outdated observations to generate incorrect incidents or notifications.
We will provide further updates as recovery progresses. The incident remains open until monitoring and alert delivery have been verified.
- Update
General recovered.
- Investigating
On October 18, 2026, at approximately 09:06 UTC, urgent infrastructure maintenance initiated by our hosting provider caused our primary server to shut down, temporarily interrupting access to StatusPage.me and customer-hosted status pages.
The server restarted at approximately 09:18 UTC, and PostgreSQL became available at 09:20 UTC. However, several application services did not recover automatically because they attempted to start before the database was ready.
Public status-page serving has since been restored, but our monitoring and incident-processing systems remain partially unavailable.
Some regional monitoring agents continue to submit results, but a significant number of monitors are not receiving scheduled checks. Automated incident detection, status updates, and notifications may therefore be delayed or unavailable.
We have identified the recovery failure and are working on a controlled restoration of our monitoring scheduler. We are taking additional precautions to prevent outdated monitoring results from generating incorrect incidents or notifications.
Monitoring history and uptime charts may contain gaps during the affected period. We will audit these gaps using recorded observations rather than assuming that missing data represents successful checks.
We will keep this incident open until monitoring, incident processing, and notification delivery have been verified end to end.
There is currently no confirmed restoration time.
We apologize for the disruption and will publish a detailed postmortem explaining the causes, customer impact, and preventive measures after complpete recovery.