bgpreport

Network · data from 2026-11-12

AS6462 National Geographic Society

Registry name: NATGEOGRAPH-AS - National Geographic Society, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS6462, 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.
104.192.166.0/23 No ROA RIR databaseARIN 673 100% 67

AS-SET

AS6462'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 9 are in fix.csv.

  • ROA: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none104.192.166.0/23No ROA covers it. Add a ROA for AS6462, maxLength 23.673 of 673

Route objects not announced

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

104.192.164.0/23RADBNo ROA
206.136.32.0/22RADBNo ROA
206.136.32.0/23RADBNo ROA
206.136.34.0/24RADBNo ROA
207.24.88.0/22RADBNo ROA
207.24.88.0/24RADBNo ROA
207.24.90.0/24RADBNo ROA
207.24.91.0/24RADBNo ROA

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.