bgpreport

Network · data from 2026-11-12

AS30016 AS01-NATC-4-NA - North American Telecommunications Corporation

Registry name: AS01-NATC-4-NA - North American Telecommunications Corporation, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30016, 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.

8.7.223.0/24 No ROA None 673 100% 67
8.10.62.0/24 No ROA None 673 100% 67
204.10.152.0/24 No ROA Nonecovered by 204.10.152.0/22 673 100% 67
204.10.154.0/24 No ROA Nonecovered by 204.10.152.0/22 673 100% 67
204.10.155.0/24 No ROA Nonecovered by 204.10.152.0/22 673 100% 67
204.10.156.0/24 No ROA Nonecovered by 204.10.156.0/23 673 100% 67
208.73.24.0/24 No ROA Nonecovered by 208.73.24.0/22 673 100% 67
208.73.27.0/24 No ROA Nonecovered by 208.73.24.0/22 673 100% 67
204.10.158.0/24 No ROA Other IRR onlyRADB 550 82% 67
204.10.159.0/24 No ROA Other IRR onlyRADB 550 82% 67

AS-SET

AS30016 isn't in PeeringDB, where networks name their 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 25 are in fix.csv.

  • ROA: none10
  • Route object: none8
  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none8.7.223.0/24No ROA covers it. Add a ROA for AS30016, maxLength 24.673 of 673
Route object: none8.7.223.0/24No route object for it. Add a route object with origin AS30016 in the RIR database for the space.673 of 673
ROA: none8.10.62.0/24No ROA covers it. Add a ROA for AS30016, maxLength 24.673 of 673
Route object: none8.10.62.0/24No route object for it. Add a route object with origin AS30016 in the RIR database for the space.673 of 673
ROA: none204.10.152.0/24No ROA covers it. Add a ROA for AS30016, maxLength 24.673 of 673
Route object: none204.10.152.0/24No route object for it. A route object for 204.10.152.0/22 with origin AS30016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30016 in the RIR database for the space.673 of 673
ROA: none204.10.154.0/24No ROA covers it. Add a ROA for AS30016, maxLength 24.673 of 673
Route object: none204.10.154.0/24No route object for it. A route object for 204.10.152.0/22 with origin AS30016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30016 in the RIR database for the space.673 of 673
ROA: none204.10.155.0/24No ROA covers it. Add a ROA for AS30016, maxLength 24.673 of 673
Route object: none204.10.155.0/24No route object for it. A route object for 204.10.152.0/22 with origin AS30016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30016 in the RIR database for the space.673 of 673
ROA: none204.10.156.0/24No ROA covers it. Add a ROA for AS30016, maxLength 24.673 of 673
Route object: none204.10.156.0/24No route object for it. A route object for 204.10.156.0/23 with origin AS30016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30016 in the RIR database for the space.673 of 673
ROA: none208.73.24.0/24No ROA covers it. Add a ROA for AS30016, maxLength 24.673 of 673
Route object: none208.73.24.0/24No route object for it. A route object for 208.73.24.0/22 with origin AS30016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30016 in the RIR database for the space.673 of 673
ROA: none208.73.27.0/24No ROA covers it. Add a ROA for AS30016, maxLength 24.673 of 673
Route object: none208.73.27.0/24No route object for it. A route object for 208.73.24.0/22 with origin AS30016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30016 in the RIR database for the space.673 of 673
ROA: none204.10.158.0/24No ROA covers it. Add a ROA for AS30016, maxLength 24.550 of 673
Route object: RIR204.10.158.0/24Route object only in RADB. Add it in the RIR database for the space.550 of 673
ROA: none204.10.159.0/24No ROA covers it. Add a ROA for AS30016, maxLength 24.550 of 673
Route object: RIR204.10.159.0/24Route object only in RADB. Add it in the RIR database for the space.550 of 673

Route objects not announced

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

204.10.152.0/21ALTDBNo ROA
204.10.152.0/22RADBNo ROA
204.10.156.0/23RADBNo ROA
206.74.251.0/24RADBNo ROA
208.73.24.0/22RADBNo 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.