BANKING-CIRCLE

BANKING-CIRCLE-GTT
BGP inherited
Cluster stats
Netblocks7
All fragments 8 blocks across 2 clusters
Cluster ID211249324
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
212.222.48.240/28 BANKING-CIRCLE-GTT RIPE ASSIGNED PA ● low
212.222.54.16/28 BANKING-CIRCLE-GTT RIPE ASSIGNED PA ● low
212.222.95.112/28 BANKING-CIRCLE-GTT RIPE ASSIGNED PA ● low
212.222.237.192/28 BANKING-CIRCLE-GTT RIPE ASSIGNED PA ● low
212.222.237.208/28 BANKING-CIRCLE-GTT RIPE ASSIGNED PA ● low
2001:668:1f:fd70::/64 BANKING-CIRCLE-GTT RIPE ASSIGNED ● low
2001:668:1f:fd71::/64 BANKING-CIRCLE-GTT RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “BANKING CIRCLE” — 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 (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

AS3257-IPAM-MNT DUMY-RIPE DUMY-RIPE