Pegasuswave

Data as of 2026-09-06
Registry
This organisation
Netblocks9
IPv6 6 prefixes (largest 2001:de8:1:1::104/128)
Also registered under this name 12 netblocks across 2 separate records
Record ID239811480
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
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 (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.27.171.124/32 Pegasuswave PEERINGDB ASSIGNED ● high
103.156.182.110/32 Pegasuswave PEERINGDB ASSIGNED ● high
103.188.179.28/32 Pegasuswave PEERINGDB ASSIGNED ● high
2001:de8:1:1::104/128 Pegasuswave PEERINGDB ASSIGNED ● high
2001:dec:4000::14:148:1/128 Pegasuswave PEERINGDB ASSIGNED ● high
2401:7500:fff6::1a9/128 Pegasuswave PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:7::14a/128 Pegasuswave PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:11::21a/128 Pegasuswave PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:24::246/128 Pegasuswave PEERINGDB ASSIGNED ● high

IPv6 ranges (6)

Footprint over time

11 weekly snapshots · JSON
9 +1 netblocks since 2026-07-05
2026-07-05 peak 9 2026-09-06

Network trust

what's this?
RPKI hygiene: F how networks compare →
11.1% of checked blocks have valid RPKI ROA coverage (1 of 9)
No discrepancies found among checked blocks.

NIC Handles

AS140148