bgpreport

Network · data from 2026-11-12

AS15930 WIPLINE-AS WIPLINE, LLC

Registry name: WIPLINE-AS WIPLINE, LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS15930, 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.
185.24.182.0/24 Invalid: maxLength Nonecovered by 185.24.180.0/22 69 10% 36
89.18.128.0/19 Valid RIR databaseRIPE 673 100% 66
89.18.128.0/21 Valid RIR databaseRIPE 673 100% 67
89.18.136.0/21 Valid RIR databaseRIPE 673 100% 66
89.18.143.0/24 Valid RIR databaseRIPE 673 100% 67
89.18.144.0/21 Valid RIR databaseRIPE 673 100% 67
89.18.152.0/21 Valid RIR databaseRIPE 673 100% 66
89.18.156.0/24 Valid RIR databaseRIPE 673 100% 67
185.24.180.0/22 Valid RIR databaseRIPE 673 100% 66
185.24.180.0/24 Valid RIR databaseRIPE 673 100% 67
2a00:65a0::/32 Valid RIR databaseRIPE 333 52% 63
89.18.159.0/24 Valid RIR databaseRIPE 124 18% 40

AS-SET

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

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: maxLength185.24.182.0/24ROA 185.24.180.0/22 AS15930 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 185.24.182.0/24.69 of 673
Route object: none185.24.182.0/24No route object for it. A route object for 185.24.180.0/22 with origin AS15930 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15930 in the RIR database for the space.69 of 673

Route objects not announced

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

89.18.131.0/24RIPEInvalid: maxLength
89.18.134.0/24RIPEInvalid: maxLength
89.18.146.0/23RIPEInvalid: maxLength
89.18.148.0/24RIPEInvalid: maxLength
89.18.150.0/24RIPEInvalid: maxLength
89.18.151.0/24RIPEInvalid: maxLength
89.18.153.0/24RIPEInvalid: maxLength

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.