bgpreport

Network · data from 2026-11-12

AS402187 AANSYS-NET - AANSys Network LLC

Registry name: AANSYS-NET - AANSys Network LLC, US · not in PeeringDB

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

Announced routes

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

31.58.99.0/24 Invalid: origin Other origin only 14 2%low visibility 13
103.102.132.0/24 Invalid: origin Other origin only 10 1%low visibility 11
95.134.154.0/24 Invalid: origin None 2 0%low visibility 2
191.96.105.0/24 Valid RIR databaseRADB, RIPE 672 100% 66

AS-SET

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

  • ROA: origin3
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin31.58.99.0/24ROAs covering it name AS834, AS146996, not AS402187. If AS402187 should announce it, add a ROA for AS402187.14 of 673
Route object: none31.58.99.0/24Route objects for it name AS146996. Add a route object with origin AS402187 in the RIR database for the space.14 of 673
ROA: origin103.102.132.0/24ROAs covering it name AS4213, AS9009, AS21769, AS54252, AS64267, AS397630, not AS402187. If AS402187 should announce it, add a ROA for AS402187.10 of 673
Route object: none103.102.132.0/24Route objects for it name AS4213, AS9009, AS54252, AS64267, AS397630. Add a route object with origin AS402187 in the RIR database for the space.10 of 673
ROA: origin95.134.154.0/24ROAs covering it name AS834, not AS402187. If AS402187 should announce it, add a ROA for AS402187.2 of 673
Route object: none95.134.154.0/24No route object for it. Add a route object with origin AS402187 in the RIR database for the space.2 of 673

Route objects not announced

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

23.153.124.0/24ARINValid

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.