Multi-Region Verification (Smart Retries)
Eliminate false alarms with supaguard's Multi-Region Verification. Learn how our 'instant teleportation' protocol confirms real outages before alerting your team.
supaguard uses Multi-Region Verification (often called Smart Retries) to eliminate the most common pain point in synthetic monitoring: false alarms.
The Problem: Localized Flakiness
In traditional monitoring, a "check" is binary: it passes or it fails. If a check fails, you get an alert immediately. However, the internet is not a single point; it's a web of connections. A check might fail because of:
- A DNS server in AWS
us-east-1glitched for 2 seconds. - A specific CDN node in New York timed out.
- A localized ISP issue in Virginia.
Competitors like Datadog and Checkly often solve this with "temporal retries"—waiting a few seconds and trying again from the same spot. But if the local node is the problem, you still get a false alarm.
The Solution: Instant Teleportation
When supaguard detects a failure, we don't just wait. We teleport. We initiate our Multi-Region Verification Protocol:
- Initial Failure: A check fails in Location A (e.g., San Francisco).
- Instant Teleportation: We instantaneously spin up a new browser instance in a completely different geographic hub, such as Location B (e.g., London) or Location C (e.g., Mumbai).
- Cross-Continent Confirmation:
- Transient (No Alert): If the secondary location passes, we mark the initial failure as a "Localized Glitch" and do not alert you.
- Global (Critical Alert): If the secondary location also fails, we confirm a true global outage and trigger your alert policy immediately.
Why This Wins
- Zero-Noise Monitoring: You only wake up if your customers are actually affected, regardless of where they are.
- Infrastructure Proof: Distinguishes between your application being "down" and a cloud provider's region having a "bad day."
- Built-in Intelligence: No manual configuration required. Every check on the Startup and Scale plans includes this "Teleportation Protocol" by default.
[!TIP] Use our Global Network page to see the specific regions available for verification.
Frequently Asked Questions
Q: How does this differ from traditional retry logic? A: Traditional retries execute the same script from the same location after a delay. If the issue is a localized ISP outage, it will still fail. Multi-Region Verification immediately runs the check from a completely different geographic zone, ensuring the failure is global.
Q: Does Multi-Region Verification cost extra? A: No. Smart retries are built into our core platform to ensure high-fidelity alerting. They are included by default on Startup and Scale plans.
Q: What happens if the verification check also fails? A: If both the initial check and the verification check fail across different regions, supaguard confirms a global outage and immediately triggers your configured alert policies (e.g., Slack, PagerDuty).
Monitoring as Code vs. AI-Native Monitoring
Compare Checkly's Monitoring as Code (MaC) with supaguard's AI-Native approach. Learn which strategy is better for your team's reliability and developer experience.
Synthetic Monitoring vs. APM: The Experience Gap
Understand the difference between backend observability (APM) and frontend reliability (Synthetics). Learn why supaguard is essential even if you already use Datadog or New Relic.