Zabbly
Cluster stats
Netblocks11
Cluster ID191664987
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-07-06

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.45.148.0/24 Zabbly BGP ANNOUNCED ● high
198.179.18.121/32 Zabbly PEERINGDB ASSIGNED ● high
2001:504:2d::18:121/128 Zabbly PEERINGDB ASSIGNED ● high
2602:fc62:a::/48 Zabbly BGP ANNOUNCED ● high
2602:fc62:b::/48 Zabbly BGP ANNOUNCED ● high
2602:fc62:c::/48 Zabbly BGP ANNOUNCED ● high
2602:fc62:d::/48 Zabbly BGP ANNOUNCED ● high
2602:fc62:ee::/48 Zabbly BGP ANNOUNCED ● high
2602:fc62:ef::/48 Zabbly BGP ANNOUNCED ● high
2602:fc62:fe::/48 Zabbly BGP ANNOUNCED ● high
2602:fc62:ff::/48 Zabbly BGP ANNOUNCED ● high

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (11 of 11)
No discrepancies found among checked blocks.

NIC Handles

AS399760 AS399760