bgpreport

Network · data from 2026-11-12

AS18851 ICORE-ASN-1 - iCore Networks, Inc.

Registry name: ICORE-ASN-1 - iCore Networks, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18851, 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.
72.5.150.0/23 No ROA Other IRR onlyRADB 673 100% 70
104.192.48.0/22 No ROA Other IRR onlyRADB 673 100% 70
173.233.48.0/20 No ROA Other IRR onlyRADB 673 100% 70
204.16.176.0/22 No ROA Other IRR onlyRADB 673 100% 70
208.73.108.0/22 No ROA Other IRR onlyRADB 673 100% 70
208.78.144.0/21 No ROA Other IRR onlyRADB 673 100% 70
208.89.200.0/21 No ROA Other IRR onlyRADB 673 100% 70

AS-SET

AS18851 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 26 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none72.5.150.0/23No ROA covers it. Add a ROA for AS18851, maxLength 23.673 of 673
Route object: RIR72.5.150.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none104.192.48.0/22No ROA covers it. Add a ROA for AS18851, maxLength 22.673 of 673
Route object: RIR104.192.48.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.233.48.0/20No ROA covers it. Add a ROA for AS18851, maxLength 20.673 of 673
Route object: RIR173.233.48.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.16.176.0/22No ROA covers it. Add a ROA for AS18851, maxLength 22.673 of 673
Route object: RIR204.16.176.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.73.108.0/22No ROA covers it. Add a ROA for AS18851, maxLength 22.673 of 673
Route object: RIR208.73.108.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.78.144.0/21No ROA covers it. Add a ROA for AS18851, maxLength 21.673 of 673
Route object: RIR208.78.144.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.89.200.0/21No ROA covers it. Add a ROA for AS18851, maxLength 21.673 of 673
Route object: RIR208.89.200.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

66.150.116.0/24RADBNo ROA
104.192.48.0/24RADBNo ROA
104.192.49.0/24RADBNo ROA
173.233.57.0/24RADBNo ROA
204.16.176.0/23RADBNo ROA
204.16.176.0/24RADBNo ROA
204.16.177.0/24RADBNo ROA
204.16.177.0/27RADBNo ROA
204.16.178.0/23RADBNo ROA
204.16.178.0/24RADBNo ROA
204.16.179.0/24RADBNo ROA
204.145.160.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.