Pegasuswave

Registry
Cluster stats
Netblocks8
All fragments 11 blocks across 2 clusters
Cluster ID208803654
RegistryPEERINGDB
Customersfind customers using 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

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ 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:24::246/128 Pegasuswave PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “Pegasuswave” — 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.

Network trust

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

NIC Handles

AS140148