DATA
Data Methodology
Last updated: April 4, 2026
This page documents where Peerfloor’s carrier data comes from, how it’s collected, and what we cannot yet independently verify. It is written for network operators evaluating whether to trust data on this platform. We publish it because verifiable sources and explicit limitations matter more to this audience than completeness.
Primary Data Sources
bgp.tools
The primary source for all carrier-facing BGP data: prefix counts, AS cone rank, peer counts, RPKI status, BGP community support, and content provider reach. All requests use a polite User-Agent header identifying Peerfloor. This is the most authoritative BGP data source we use, and it is credited on every carrier profile section it powers.
RouteViews — University of Oregon (CC-BY 4.0)
Route collector data used for path length analysis and prefix count verification. Average path length derived from RouteViews is displayed on carrier profile pages with explicit attribution. Licensed under CC-BY 4.0; attribution is included wherever RouteViews-derived data appears.
Operator-contributed data
Information voluntarily submitted by carriers and buyers. Currently minimal ahead of launch. When displayed, it is labeled as operator-contributed and not treated as independently verified.
Collection Process
BGP data from bgp.tools is refreshed weekly using a polite User-Agent header (Peerfloor/1.0 carriers@peerfloor.com). This is the primary source for all carrier-facing BGP metrics: prefix counts, AS cone rank, peer counts, RPKI status, and BGP community support.
RouteViews data is refreshed nightly via an automated pipeline. It provides path length analysis and prefix count verification. Where a RouteViews-derived metric appears on a carrier page, it is labeled with explicit attribution.
Carrier documentation (operational capabilities, facility presence, port sizes) is manually reviewed. It is updated when carriers publish changes or when operators flag corrections.
Each section on a carrier profile page shows its own source attribution and verification date. There is no real-time data streaming.
Known Limitations
Coverage and PoP data
Facility presence and port availability are sourced from carrier websites and public documentation. They are not independently verified at every facility. Discrepancies should be reported.
Single-source data points
Where a metric on a carrier profile page comes from a single unverified source, this is noted in the section’s source attribution. We do not present single-source data as confirmed without labeling it.
Operator-contributed data
Carrier-submitted information has not been independently verified. It is labeled as operator-contributed wherever it appears.
Carrier Display Order
Carriers are listed alphabetically by display name on all comparison and planner views. Display name defaults to the carrier’s registered name and may be adjusted for common-use abbreviations (for example, HE instead of Hurricane Electric). No ranking or scoring is applied. Carriers are not ordered by performance, relationship status, or any other editorial judgment.
Neutrality
Carrier data displayed on Peerfloor is sourced from public BGP records and verified routing databases. No carrier pays for placement, priority, or preferential treatment in search results, comparisons, or profile rankings.
All comparisons present carriers in alphabetical order by display name. No scoring, ranking, or editorial judgment is applied to carrier listings. The platform does not steer users toward any particular provider. Commercial relationships with carriers do not influence how data is collected, displayed, or ordered.
A Note on PeeringDB
PeeringDB data is not used in the platform. Carrier profiles link to PeeringDB pages for operator reference.
Errors and Corrections
If you find a data error, email carriers@peerfloor.com. Carrier-submitted corrections are reviewed before being applied and are labeled as operator-contributed once live.