Use cases
Monitor internet outages
Monitor internet outages with SUZU Monitor. Compare connectivity reports, undersea cables, and regional events to prepare a sourced service dependency review.
Who this workflow helps
Infrastructure analysts and continuity teams reviewing regional connectivity dependencies.
When to start
A reported internet disruption affecting a country or a region that hosts users, suppliers, or staff.
What you will produce
A connectivity incident note with the observed region, source time, possible dependencies, and provider confirmation status.
End-to-end workflow
- Define the service exposure
Record the affected region and the services or suppliers that depend on it. Open Internet Disruptions and locate the available report. A regional connectivity signal does not prove that your application is unavailable.
- Check observation time and scope
Read the outage source and timestamps. Compare the report with your own service monitoring and the provider status page. Distinguish a current observation from a retained older incident.
- Inspect infrastructure context
Use cable and datacenter locations to identify dependencies worth checking. Review original advisories before attributing the outage to a cable fault. Geographic proximity is a hypothesis, not a verified network path.
- Record cause and recovery separately
State what is observed, which cause is confirmed, and which service owner is investigating. Record recovery only after the relevant provider or your own checks establish it. Schedule a follow-up for unresolved regions.
Worked example
Illustrative scenario: a regional outage report appears near a cable landing area. Your application checks still pass from another region. Record the regional report and the test location. Ask the network provider about the affected path instead of announcing a cable failure or global service outage.
Provenance, freshness, and limits
Connectivity observations are not packet-level diagnostics. Cable geography does not reveal the active route of a customer connection. A restored regional metric does not prove that every affected service has recovered.
Check the observation time and original source before each decision. This guide describes a repeatable procedure, not a live incident report. Data availability depends on provider coverage and the selected product view.
Common question
Can the map identify the cause of an internet outage?
The map provides context and possible dependencies. Confirm the cause with the network operator or independent technical evidence before attributing it to a cable cut, power loss, or deliberate restriction.