CERTEGY

BGP inherited
Cluster stats
Netblocks9
Registered in United Kingdom (7) · Australia (2)
All fragments 18 blocks across 7 clusters
Cluster ID208938304
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
59.154.191.0/29 CERTEGY APNIC ASSIGNED NON-PORTABLE ● low
61.88.119.32/28 CERTEGY APNIC ASSIGNED NON-PORTABLE ● low
80.193.136.96/27 CERTEGY-LTD RIPE ASSIGNED PA ● low
80.194.48.192/27 CERTEGY-LTD RIPE ASSIGNED PA ● low
82.36.6.208/28 CERTEGY-LTD RIPE ASSIGNED PA ● low
82.36.14.152/30 CERTEGY-LTD RIPE ASSIGNED PA ● low
217.45.195.56/29 CERTEGY RIPE ASSIGNED PA ● low
217.46.183.224/29 CERTEGY RIPE ASSIGNED PA ● low
217.46.184.8/29 CERTEGY RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

Network trust

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

NIC Handles

AS5089-MNT AS5462-MNT BTNET-MNT DUMY-RIPE DUMY-RIPE MAINT-OPTUSCOM-AP OA3-AP OA3-AP