APX Integration SASU
BCS-CUST-VESI-1
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 15 blocks across 12 clusters |
| Cluster ID | 205309232 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a01:6940:cafa::/48 | BCS-CUST-VESI-1 | RIPE | ASSIGNED | ● medium |
| 2a01:6940:cafb::/48 | BCS-VCC-EQX-PUB1 | RIPE | ASSIGNED | ● medium |
| 178.255.130.160/27 | BCS-CUST-VESI-1 | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (2)
These blocks are registered to BCS-CUST-VESI-1 but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a01:6940:cafb::/48 /48 | authorized for AS29605 — APX Integration SASU |
| 2a01:6940:cafa::/48 /48 | authorized for AS29605 — APX Integration SASU |
NIC Handles
BT3178-RIPE
DUMY-RIPE
DUMY-RIPE
MNT-BCS