Public pages can mention broad countries or regions.
Resource · Resources
Monitoring locations and IP guidance
Understand how FTStatus reports monitoring locations and what can safely be shared publicly.
HTTPDNSSSLAPI
Logical locations stay public. Probe internals stay private.
Admin dashboards can show primary and backup probe mode.
Sensitive origin, provider, and firewall details stay private.
Watch the signal
Track the public evidence customers actually experience.
Measure the trend
Keep response, uptime, and incident context close to the decision.
Route the response
Alert the right people and publish customer-safe updates when needed.
Public location labels
Use simple labels such as country or region. Avoid publishing probe hostnames, SSH routes, or exact firewall allowlists.
Fallback behavior
The platform should accept one unified payload per logical location while retaining admin-only metadata about backup mode.
Downtime confidence
Customer-facing downtime should require quorum or repeated confirmation unless the failure is globally obvious.
Related pages
Continue building the monitoring workflow.
Ready to set up the right monitors?
Start with critical customer-facing services, then add status pages, alert routes, and managed help as reliability becomes more important.