bgpreport

Network · data from 2026-11-12

AS198015 INOXWEB-LLC Inoxweb LLC

Registry name: INOXWEB-LLC Inoxweb LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198015, 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.
2a14:9401:6000::/36 Valid Other origin only 632 99% 67
2a14:9401:7000::/36 Valid Other origin only 632 99% 67
2a14:9401:b000::/36 Valid None 631 99% 67
87.76.195.0/24 Valid RIR databaseRIPE 671 100% 66
2a14:9401:a000::/36 Valid RIR databaseRIPE 632 99% 67

AS-SET

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

  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2a14:9401:6000::/36Route objects for it name AS213488. Add a route object with origin AS198015 in the RIR database for the space.632 of 636
Route object: none2a14:9401:7000::/36Route objects for it name AS213488. Add a route object with origin AS198015 in the RIR database for the space.632 of 636
Route object: none2a14:9401:b000::/36No route object for it. Add a route object with origin AS198015 in the RIR database for the space.631 of 636

Route objects not announced

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

2a0f:7803:ff81::/48ALTDB, RADBNo 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.