bgpreport

Network · data from 2026-11-12

AS43588 iHost

Registry name: LEVEL7-AS IM Level 7 SRL, MD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43588, 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.131.7.151/32 Invalid: maxLength Nonecovered by 31.131.7.0/24 3 0%low visibility 6
87.255.76.0/24 Valid Other origin only 57 8%low visibility 33
87.255.82.0/24 Valid None 57 8%low visibility 33
31.131.7.0/24 Valid RIR databaseRIPE 673 100% 66
31.131.0.0/22 Valid RIR databaseRADB, RIPE 671 100% 68
31.131.4.0/23 Valid RIR databaseRIPE 671 100% 68
31.131.6.0/24 Valid RIR databaseRIPE 671 100% 68
91.216.47.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
91.228.108.0/22 Valid RIR databaseRIPE 671 100% 68
31.131.1.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS43588: RIPE::AS-SECURED. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS43588 isn't in the set, or no route object for AS43588 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS43588 in itNot covered
RIPE::AS-SECURED RIPE 338 Yes 3

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

  • ROA: maxLength1
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength31.131.7.151/32ROA 31.131.7.0/24 AS43588 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.131.7.151/32.3 of 673
Route object: none31.131.7.151/32No route object for it. A route object for 31.131.7.0/24 with origin AS43588 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS43588 in the RIR database for the space.3 of 673
Route object: none87.255.76.0/24Route objects for it name AS15836. Add a route object with origin AS43588 in the RIR database for the space.57 of 673
Route object: none87.255.82.0/24No route object for it. Add a route object with origin AS43588 in the RIR database for the space.57 of 673

Route objects not announced

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

31.131.0.0/21RIPENo 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.