bgpreport

Network · data from 2026-11-12

AS7859 Pair Networks

Registry name: PAIR-NETWORKS - pair Networks, US · PeeringDB

7IPv4 routes 71.4% RPKI valid · 71.4% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS7859, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS7859, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
209.68.44.0/22 No ROA None 672 100% 66
209.68.0.0/18 No ROA None 670 100% 66
65.181.188.0/22 Valid RIR databaseARIN, RADB 672 100% 66
216.146.192.0/19 Valid RIR databaseARIN 672 100% 67
66.39.0.0/17 Valid RIR databaseARIN, RADB 670 100% 66
66.39.128.0/19 Valid RIR databaseARIN, RADB 670 100% 66
216.92.0.0/16 Valid RIR databaseARIN, RADB 670 100% 66
2607:f440::/32 Valid RIR databaseARIN, RADB 633 100% 67
2607:f441::/32 Valid RIR databaseARIN 633 100% 68

AS-SET

AS7859's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 7 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none209.68.44.0/22No ROA covers it. Add a ROA for AS7859, maxLength 22.672 of 673
Route object: none209.68.44.0/22No route object for it. Add a route object with origin AS7859 in the RIR database for the space.672 of 673
ROA: none209.68.0.0/18No ROA covers it. Add a ROA for AS7859, maxLength 18.670 of 673
Route object: none209.68.0.0/18No route object for it. Add a route object with origin AS7859 in the RIR database for the space.670 of 673

Route objects not announced

Route objects with origin AS7859 whose prefix no peer sees AS7859 announce. Many are kept on purpose (backup routes, space announced only in some places).

64.130.0.0/19ARINNo ROA
65.181.128.0/18ARINNo ROA
76.75.208.0/20ARINValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.