JAT

BGP inherited
Cluster stats
Netblocks7
Registered in ME (4) · China (1) · Germany (1) · Serbia (1)
All fragments 20 blocks across 6 clusters
Cluster ID208960791
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
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
222.66.77.200/29 JAT-CO APNIC ASSIGNED NON-PORTABLE ● high
195.66.190.160/29 JAT RIPE ASSIGNED PA ● low
195.66.190.168/29 JAT RIPE ASSIGNED PA ● low
195.66.190.176/29 JAT RIPE ASSIGNED PA ● low
195.82.36.128/25 JAT RIPE ASSIGNED PA ● low
195.250.116.64/26 JAT-NET RIPE ASSIGNED PA ● low
213.149.120.80/28 JAT RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

AS8375-MNT AS8585-MNT CXX3-AP CXX3-AP DUMY-RIPE DUMY-RIPE INFOSKY-MNT MAINT-CHINANET-SH