bgpreport

Network · data from 2026-11-12

AS12284 IPNS, Inc.

Registry name: IPNS-AS - Computer Solutions / CSolutions, US · PeeringDB

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

Announced routes

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

216.162.202.0/24 No ROA Nonecovered by 216.162.202.0/23 2 0%low visibility 2
208.110.128.0/19 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
2605:5980::/32 No ROA RIR databaseARIN 635 100% 68
208.110.128.0/24 Valid RIR databaseARIN 672 100% 67
208.110.131.0/24 Valid RIR databaseARIN 672 100% 67
208.110.132.0/24 Valid RIR databaseARIN 672 100% 67
208.110.142.0/24 Valid RIR databaseARIN 672 100% 67
208.110.149.0/24 Valid RIR databaseARIN 672 100% 67
208.110.150.0/24 Valid RIR databaseARIN 672 100% 67
208.110.151.0/24 Valid RIR databaseARIN 672 100% 67
208.110.156.0/24 Valid RIR databaseARIN 672 100% 67
208.110.158.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

AS12284'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 10 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none216.162.202.0/24No ROA covers it. Add a ROA for AS12284, maxLength 24.2 of 673
Route object: none216.162.202.0/24No route object for it. A route object for 216.162.202.0/23 with origin AS12284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12284 in the RIR database for the space.2 of 673
ROA: none208.110.128.0/19No ROA covers it. Add a ROA for AS12284, maxLength 19.672 of 673
Route object: RIR208.110.128.0/19Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2605:5980::/32No ROA covers it. Add a ROA for AS12284, maxLength 32.635 of 636

Route objects not announced

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

8.7.83.0/24NTTCOMNo ROA
199.104.64.0/23NTTCOM, RADBNo ROA
209.54.142.0/24NTTCOMNo ROA
216.162.202.0/23ARINNo ROA
216.162.206.0/23ARINNo 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.