AWS-BYOIP
BGP inherited
Cluster stats
| Netblocks | 8 |
| Cluster ID | 205684882 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-13
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 109.68.66.0/24 | AWS-BYOIP | RIPE | ASSIGNED PA | ● low |
| 109.68.67.0/24 | AWS-BYOIP | RIPE | ASSIGNED PA | ● low |
| 109.68.69.0/24 | AWS-BYOIP | RIPE | ASSIGNED PA | ● low |
| 109.68.70.0/24 | AWS-BYOIP | RIPE | ASSIGNED PA | ● low |
| 109.68.71.0/24 | AWS-BYOIP | RIPE | ASSIGNED PA | ● low |
| 145.224.192.0/19 | AWS-BYOIP | RIPE | LEGACY | ● low |
| 145.224.192.0/24 | AWS-BYOIP | RIPE | LEGACY | ● low |
| 2a04:e4c4:5::/48 | AWS_BYOIP | RIPE | ASSIGNED | ● low |
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.
- SEYMOURS-AWS-BYOIP-LHR-143 via Amazon.com, Inc. sub-allocation
- Jaggaer Aws Byoip 1 via Amazon.com, Inc. sub-allocation
- IMPULSO-AWS-BYOIP-109-232-88-0-24 via Amazon.com, Inc. sub-allocation
- SEYMOURS-AWS-BYOIPV6-LHR-143 via Amazon.com, Inc. sub-allocation
- SEYMOURS-AWS-BYOIPV6-LHR-0E27-143 via Amazon.com, Inc. sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(8 of 8)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
OPENDNS-MNT
SFDC-MNT
XPUK-MNT