bgpreport

Network · data from 2026-11-12

AS58439 ICNC

Registry name: ICNC-AS - ICNC LLC, MN · PeeringDB

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

Announced routes

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

183.177.96.0/21 Valid RIR databaseAPNIC, RADB 672 100% 67
103.194.176.0/22 Valid RIR databaseAPNIC 670 100% 67
183.177.104.0/22 Valid RIR databaseAPNIC, RADB 670 100% 67
183.177.108.0/23 Valid RIR databaseAPNIC, RADB 670 100% 67
183.177.111.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
2402:8880::/32 Valid RIR databaseAPNIC 636 100% 67

AS-SET

AS58439'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 39 are in fix.csv.

  • Route object: not announced39

Route objects not announced

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

103.194.176.0/23APNICInvalid: maxLength
103.194.176.0/24APNICInvalid: maxLength
103.194.177.0/24APNICInvalid: maxLength
103.194.178.0/23APNICInvalid: maxLength
103.194.178.0/24APNICInvalid: maxLength
103.194.179.0/24APNICInvalid: maxLength
183.177.96.0/20APNIC, RADBValid
183.177.96.0/22APNIC, RADBValid
183.177.96.0/23APNIC, RADBValid
183.177.96.0/24APNIC, RADBValid
183.177.97.0/24APNIC, RADBValid
183.177.98.0/23APNIC, RADBValid
183.177.98.0/24APNIC, RADBValid
183.177.99.0/24APNIC, RADBValid
183.177.100.0/22APNIC, RADBValid
183.177.100.0/23APNIC, RADBValid
183.177.100.0/24APNIC, RADBValid
183.177.101.0/24APNIC, RADBValid
183.177.102.0/23APNIC, RADBValid
183.177.102.0/24APNIC, RADBValid
183.177.103.0/24APNIC, RADBValid
183.177.104.0/21APNIC, RADBValid
183.177.104.0/23APNIC, RADBValid
183.177.104.0/24APNIC, RADBValid
183.177.105.0/24APNIC, RADBValid
183.177.106.0/23APNIC, RADBValid
183.177.106.0/24APNIC, RADBValid
183.177.107.0/24APNIC, RADBValid
183.177.108.0/22APNIC, RADBValid
183.177.108.0/24APNIC, RADBValid
183.177.109.0/24APNIC, RADBValid
183.177.110.0/23APNIC, RADBValid
183.177.110.0/24APNIC, RADBValid
2402:8880::/33APNICValid
2402:8880::/34APNICValid
2402:8880:4000::/34APNICValid
2402:8880:8000::/33APNICValid
2402:8880:8000::/34APNICValid
2402:8880:c000::/34APNICValid

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.