Network · data from 2026-11-12

AS29605 BCS Technologies

Registry name: Axians_Cloud_Services_Provider APX Integration SASU, FR · PeeringDB

18IPv4 routes 100.0% RPKI valid · 94.4% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS29605, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS29605, 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.87.90.0/24	Valid	Nonecovered by 185.87.88.0/22	673 100%	67
46.19.176.0/22	Valid	RIR databaseRIPE	673 100%	67
46.19.180.0/22	Valid	RIR databaseRIPE	673 100%	67
89.107.168.0/22	Valid	RIR databaseRIPE	673 100%	67
89.107.172.0/22	Valid	RIR databaseRIPE	673 100%	67
93.188.168.0/22	Valid	RIR databaseRIPE	673 100%	67
93.188.172.0/22	Valid	RIR databaseRIPE	673 100%	67
178.255.128.0/21	Valid	RIR databaseRIPE	673 100%	67
185.48.44.0/23	Valid	RIR databaseRIPE	673 100%	67
185.48.46.0/23	Valid	RIR databaseRIPE	673 100%	67
185.87.88.0/22	Valid	RIR databaseRIPE	673 100%	67
193.110.140.0/24	Valid	RIR databaseRIPE	673 100%	67
212.67.32.0/21	Valid	RIR databaseRIPE	673 100%	67
212.67.39.0/24	Valid	RIR databaseRIPE	673 100%	67
212.67.40.0/21	Valid	RIR databaseRIPE	673 100%	67
217.19.48.0/21	Valid	RIR databaseRIPE	673 100%	67
217.19.56.0/21	Valid	RIR databaseRIPE	673 100%	67
185.207.44.0/23	Valid	RIR databaseRIPE	671 100%	67
2a01:6940::/32	Valid	RIR databaseRIPE	633 100%	68

AS-SET

PeeringDB's irr_as_set for AS29605: AS-ACSP. 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 (AS29605 isn't in the set, or no route object for AS29605 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.

Name	Database	ASNs	Sets	Route objects	AS29605 in it	Not covered
AS-ACSP	In no IRR database read today.

Name

Database

ASNs

Sets

Route objects

AS29605 in it

Not covered

AS-ACSP

In no IRR database read today.

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: none1
AS-SET: not found1

Change	Prefix or set	Detail	Full-table peers
Route object: none	185.87.90.0/24	No route object for it. A route object for 185.87.88.0/22 with origin AS29605 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29605 in the RIR database for the space.	673 of 673
AS-SET: not found	AS-ACSP	PeeringDB names AS-ACSP; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: none

185.87.90.0/24

No route object for it. A route object for 185.87.88.0/22 with origin AS29605 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29605 in the RIR database for the space.

673 of 673

AS-SET: not found

AS-ACSP

PeeringDB names AS-ACSP; no IRR database read has it.

Route objects not announced

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