What Does 'Monitoring Interrupted' Mean?
Why a monitor can show an Unknown status, how Pingara tells a probe outage apart from your site being down, and what happens when checks resume.
Pingara checks your sites from monitoring probes in multiple regions. Occasionally one of those probes has a problem of its own — a hardware failure, a network outage in its region, or maintenance gone wrong. When that happens to every region your monitor is configured to use, Pingara can no longer check your site at all.
Rather than keep showing the last known status (which could silently go stale), your monitor switches to a distinct status: Unknown.
Unknown is not Down
The two statuses make opposite claims:
| Status | What it means |
|---|---|
| Down | Our probes reached out to your site and it failed — confirmed by live checks |
| Unknown | Our probe infrastructure cannot currently run checks — we have no information about your site either way |
Every Down alert includes which regions confirmed the failure (for example, "Confirmed by 2 of 3 configured monitoring regions"), so you always know a Down page is based on live evidence from working probes.
What happens during an interruption
When Pingara confirms a probe region outage affecting your monitor:
- You get one notification through your normal alert channels, stating clearly that this is a Pingara infrastructure issue — not a signal that your site is down
- The monitor shows "Unknown" on your dashboard, with a banner listing every affected monitor
- The sidebar "Platform health" light turns amber (or red for a full outage), with per-region detail on hover
- Escalation reminders pause for any incident that was already open — we won't keep paging you while we can't gather new evidence
- Your public status page is unaffected — it keeps showing the last confirmed state. Your visitors aren't shown Pingara's infrastructure problems
What happens when checks resume
Recovery is automatic — no action is needed from you:
- The probe comes back and checks run again
- The very first result clears the Unknown state — a successful check sets the monitor to Up, failures count toward the normal detection thresholds
- You get one "monitoring resumed" notification
The gap in your history
Checks that never ran can't be backfilled. The interruption window is a genuine blind spot: uptime percentages and response-time charts simply have no data for it, and an outage of your site during that window would not have been detected or recorded. Interrupted periods are not counted as downtime in your uptime or SLA numbers.
Reducing your exposure
A monitor is only fully blinded when all of its configured regions are affected at once. On the Pro plan you can select multiple regions per monitor — with 3 or more regions, losing any single region leaves detection fully operational.
Next Steps
- Setting Up Alerts — Create and configure alert policies
- Understanding Incidents — How detection and recovery work