The Internet Health Report helps network operators to monitor network conditions. Network performance data is collected with RIPE Atlas
. and analyzed with a set of tools pinpointing delay changes, forwarding anomalies, network disconnections and routing changes.
How do I get my network monitored?
Delay changes, forwarding anomalies, network disconnections
The data we analyze is collected with RIPE Atlas. Networks observed in the builtin and anchoring measurements are likely to appear in the delay change and forwarding anomaly reports. And networks hosting more than 10 public probes appear in the network disconnection reports.
The best way to ensure that your network is monitored is to host an anchor (delay changes, forwarding anomalies) and at least 10 probes (network disconnection).
We use BGP data to monitor Internet routing infrastructure. If your AS is publicly advertising IP space then it should be already monitored by our system.
What the graphs mean?
Each graph represents a different aspect of network conditions, we provide documentation for each of them:
How it works?
We have several research papers describing our monitoring techniques:
- Romain Fontugne, Emile Aben, Cristel Pelsser, Randy Bush,
Pinpointing Delay and Forwarding Anomalies Using Large-Scale Traceroute Measurements. ACM IMC 2017, London, UK (bibtex).
- Anant Shah, Romain Fontugne, Emile Aben, Cristel Pelsser, Randy Bush, Disco: Fast, Good, and Cheap Outage Detection, TMA 2017 (bibtex).
- Romain Fontugne, Anant Shah, Emile Aben, The (thin) Bridges of AS Connectivity: Measuring Dependency using AS Hegemony, Proceedings of PAM'18. Berlin, Germany. March 2018 (bibtex).
- Romain Fontugne, Anant Shah, Emile Aben, AS Hegemony: A Robust Metric for AS Centrality, SIGCOMM Posters and Demos '17 (bibtex).
If you publish material using data from the Internet Health Report, then, help others to obtain the same data sets and replicate your experiments by citing of the above papers.
Our implementations are also publicly available on github: