bgpreport

Network · data from 2026-11-12

AS272884 AS272884 - LEOWISP SAS

Registry name: AS272884 - LEOWISP SAS, CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272884, 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.
181.224.92.0/24 Valid Nonecovered by 181.224.92.0/23 673 100% 67
181.224.93.0/24 Valid Nonecovered by 181.224.92.0/23 673 100% 67
181.224.92.0/23 Valid RIR databaseLACNIC, RADB 673 100% 67
2803:ba90::/32 Valid RIR databaseLACNIC 636 100% 69

AS-SET

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

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none181.224.92.0/24No route object for it. A route object for 181.224.92.0/23 with origin AS272884 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272884 in the RIR database for the space.673 of 673
Route object: none181.224.93.0/24No route object for it. A route object for 181.224.92.0/23 with origin AS272884 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272884 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS272884 is announced.

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.