VERIZON-NET6_2-SDE-P2P
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 4 blocks across 4 clusters |
| Cluster ID | 206009931 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 |
|---|---|---|---|---|
| 2a02:2ab8:30f::/48 | VERIZON-NET6_2-SDE-P2P | RIPE | ASSIGNED | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “VERIZON NET6 2” — 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.
- VERIZON-NET6_2-DUB-P2P 1 blocks
- VERIZON-NET6_2-LND-P2P 1 blocks
- VERIZON-NET6_2-MUC-P2P 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.
- VERIZON-NET6_1-RTM-P2P sub-allocation
- VERIZON-NET6_4-MAD-P2P sub-allocation
- VERIZON-NET6_2-DUB-P2P sub-allocation
- VERIZON-NET6_2-LND-P2P sub-allocation
- VERIZON-NET6_5-BRU-P2P sub-allocation
- VERIZON-NET6_7-MLN-P2P sub-allocation
- VERIZON-NET6_4-FFT-P2P sub-allocation
NIC Handles
DUMY-RIPE
DUMY-RIPE
IWAY-NOC