A failed check is one observation. A confirmed outage is a monitoring decision made after Uptime Basics has enough evidence to reduce the chance of a false alarm.
What happens after a failed check
When the primary check fails, Uptime Basics records the result and can request confirmation from additional monitoring regions. The current production policy uses Canada as the primary region with confirmation from Eastern United States and Western United States.
The regional policy requires at least two of the three regions to agree that the target is failing. The monitor also requires three consecutive failed monitoring results before changing to Down.
Why the monitor may remain Up
The monitor can remain Up when:
- A later check succeeds before the consecutive-failure threshold is reached.
- A confirmation region reaches the website successfully.
- The primary request encounters a brief network or routing problem that is not reproduced elsewhere.
- A HEAD request is rejected but the automatic GET fallback succeeds.
The original failed check remains visible in Detailed Logs because it is useful diagnostic information. Keeping that record does not mean Uptime Basics ignored the failure; it means the evidence did not confirm a full outage.
When an incident opens
An availability incident opens when the failure and regional confirmation requirements are met. The monitor changes to Down and enabled alert channels can send a downtime notification.
The incident page then provides:
- The failure category and recommended action.
- Regional confirmation details.
- DNS, TCP, TLS, and HTTP diagnostics where available.
- Checks around the beginning and end of the incident.
- The activity history for alerts and recovery.
How recovery works
Successful checks move the monitor back to Up and resolve the open incident. Recovery notifications are kept separate from the original downtime notification so customers can see when service returned.