bgpreport

Network · data from 2026-11-12

AS56987 Abaclouda

Registry name: AS-ABACLOUDA ABACLOUDA SAS, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56987, 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.
5.180.57.6/31 Invalid: maxLength Nonecovered by 5.180.57.0/24 2 0%low visibility 1
5.180.57.36/32 Invalid: maxLength Nonecovered by 5.180.57.0/24 2 0%low visibility 1
5.180.58.6/31 Invalid: maxLength Nonecovered by 5.180.58.0/23 2 0%low visibility 1
5.180.58.36/32 Invalid: maxLength Nonecovered by 5.180.58.0/23 2 0%low visibility 1
5.180.57.0/24 Valid RIR databaseRIPE 673 100% 66
5.180.58.0/23 Valid RIR databaseRIPE 673 100% 66
185.140.248.0/24 Valid RIR databaseRIPE 673 100% 66
185.197.150.0/24 Valid RIR databaseRIPE 673 100% 66
2a0c:3d00::/29 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS56987: AS-ABACLOUDA. 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 (AS56987 isn't in the set, or no route object for AS56987 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 objectsAS56987 in itNot covered
AS-ABACLOUDA RIPElists itself further down1 member set in no database: AS-PLAINELIMAGNE 2411216 Yes 4

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: maxLength4
  • Route object: none4
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
ROA: maxLength5.180.57.6/31ROA 5.180.57.0/24 AS56987 has maxLength 24; the route is a /31. Raise the maxLength, or add a ROA for 5.180.57.6/31.2 of 673
Route object: none5.180.57.6/31No route object for it. A route object for 5.180.57.0/24 with origin AS56987 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS56987 in the RIR database for the space.2 of 673
ROA: maxLength5.180.57.36/32ROA 5.180.57.0/24 AS56987 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 5.180.57.36/32.2 of 673
Route object: none5.180.57.36/32No route object for it. A route object for 5.180.57.0/24 with origin AS56987 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS56987 in the RIR database for the space.2 of 673
ROA: maxLength5.180.58.6/31ROA 5.180.58.0/23 AS56987 has maxLength 23; the route is a /31. Raise the maxLength, or add a ROA for 5.180.58.6/31.2 of 673
Route object: none5.180.58.6/31No route object for it. A route object for 5.180.58.0/23 with origin AS56987 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS56987 in the RIR database for the space.2 of 673
ROA: maxLength5.180.58.36/32ROA 5.180.58.0/23 AS56987 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 5.180.58.36/32.2 of 673
Route object: none5.180.58.36/32No route object for it. A route object for 5.180.58.0/23 with origin AS56987 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS56987 in the RIR database for the space.2 of 673
AS-SET: missing memberAS-ABACLOUDAAS-ABACLOUDA (RIPE) lists AS-PLAINELIMAGNE; no IRR database read has it.

Route objects not announced

Every route object with origin AS56987 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.