CONNECT MOBILITY
BGP inherited
Cluster stats
| Netblocks | 4 |
| Cluster ID | 207730511 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 206.81.82.41/32 | CONNECT MOBILITY | PEERINGDB | ASSIGNED | ● high |
| 206.126.225.170/32 | CONNECT MOBILITY | PEERINGDB | ASSIGNED | ● high |
| 2001:504:16::6:17df/128 | CONNECT MOBILITY | PEERINGDB | ASSIGNED | ● high |
| 2001:504:2f::39:9327:1/128 | CONNECT MOBILITY | PEERINGDB | ASSIGNED | ● high |
Possibly related to this organisation
what's this?Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- Axiansconnect Vesi Vf Mobility via MASSELIN COMMUNICATION SAS sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
No discrepancies found among checked blocks.
NIC Handles
AS399327