AWS-PS-GM-BYOIP-L3-1
Handle
Cluster stats
| Netblocks | 1 |
| All fragments | 17 blocks across 16 clusters |
| Cluster ID | 206256999 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a13:d040:10::/48 | AWS-PS-GM-BYOIP-L3-1 | RIPE | ASSIGNED | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “AWS PS GM BYOIP L3” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- AWS-PS-GM-BYOIP-L3-16 2 blocks
- AWS-PS-GM-BYOIP-L3-3 1 blocks
- AWS-PS-GM-BYOIP-L3-4 1 blocks
- AWS-PS-GM-BYOIP-L3-5 1 blocks
- AWS-PS-GM-BYOIP-L3-6 1 blocks
- AWS-PS-GM-BYOIP-L3-7 1 blocks
- AWS-PS-GM-BYOIP-L3-8 1 blocks
- AWS-PS-GM-BYOIP-L3-2 1 blocks
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.
- revenera-aws-65737-byoip-eu via Amazon.com, Inc. sub-allocation
- SEYMOURS-AWS-BYOIP-LHR-143 via Amazon.com, Inc. sub-allocation
- A2D-BYOIP-185-82-48 via BV Gaming Limited sub-allocation
- Jaggaer Aws Byoip 1 via Amazon.com, Inc. sub-allocation
- INTERNETSTIFTELSEN-BYOIP via Amazon.com, Inc. sub-allocation
- CF-BYOIP-88-211-200-0-24 sub-allocation
- CF-BYOIP-88-211-201-0-24 sub-allocation
- CF-BYOIP-88-211-202-0-24 sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
RPKI-inferred operator
Amazon.com, Inc.
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
CMOU-MNT
DUMY-RIPE
DUMY-RIPE