bgpreport

Network · data from 2026-11-12

AS401486 RAVNIX - RAVNIX LLC

Registry name: RAVNIX - RAVNIX LLC, US · not in PeeringDB

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

Announced routes

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

74.50.10.0/24 Invalid: origin None 3 0%low visibility 3
74.50.11.0/24 Invalid: origin None 3 0%low visibility 3
23.129.180.0/24 Valid RIR databaseARIN 671 100% 67
130.12.60.0/24 Valid RIR databaseARIN 671 100% 67
136.148.76.0/24 Valid RIR databaseRIPE 671 100% 67
143.20.24.0/22 Valid RIR databaseRADB, RIPE 671 100% 67
188.255.249.0/24 Valid RIR databaseRIPE 670 100% 67
2602:f7a3::/40 Valid RIR databaseARIN 636 100% 67
2a0e:f180::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

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

  • ROA: origin2
  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin74.50.10.0/24ROAs covering it name AS834, not AS401486. If AS401486 should announce it, add a ROA for AS401486.3 of 673
Route object: none74.50.10.0/24No route object for it. Add a route object with origin AS401486 in the RIR database for the space.3 of 673
ROA: origin74.50.11.0/24ROAs covering it name AS834, not AS401486. If AS401486 should announce it, add a ROA for AS401486.3 of 673
Route object: none74.50.11.0/24No route object for it. Add a route object with origin AS401486 in the RIR database for the space.3 of 673

Route objects not announced

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

16.5.4.0/24ARINValid
31.56.64.0/24RIPEValid
192.150.185.0/24ARINValid
2a09:54c6::/32RIPEInvalid: origin

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.