AS265684
Data as of 2026-08-30
Handle
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 |
| IPv6 | 3 prefixes (largest 2803:ac30::/32) |
| Cluster ID | 233056332 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| 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 · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2803:d20::/32 | AS265684 | BGP | ANNOUNCED | ● high |
| 2803:ac30::/32 | AS265684 | BGP | ANNOUNCED | ● high |
| 2803:e1c0::/32 | AS265684 | BGP | ANNOUNCED | ● high |
IPv6 ranges (3)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
Possible discrepancies (1)
These blocks are registered to AS265684 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.
| 2803:e1c0::/32 /32 | authorized for AS52468 — AS52468 |
NIC Handles
AS265684