TAG Systems

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks9 · 658 IPv4 addresses
IPv6 3 prefixes (largest 2a10:d2c0::/32)
Registered in CR (4) · LI (1) · Poland (1)
Record ID236509225
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 15 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
200.107.83.164/32 TAG Systems PEERINGDB ASSIGNED ● high
200.107.83.201/32 TAG Systems PEERINGDB ASSIGNED ● high
2801:1d:a000:1::1164/128 TAG Systems PEERINGDB ASSIGNED ● high
2801:1d:a000:1::1201/128 TAG Systems PEERINGDB ASSIGNED ● high
46.229.150.224/28 TAG_Systems-NET RIPE ASSIGNED PA ● low
168.205.64.0/24 TAG Systems ARIN REALLOCATED ● low
190.4.88.0/25 TAG Systems LACNIC REALLOCATED ● low
193.32.84.0/24 TAG Systems AG RIPE ALLOCATED PA ● low
2a10:d2c0::/32 TAG Systems AG RIPE ALLOCATED-BY-RIR ● low

IPv6 ranges (3)

Footprint over time

11 weekly snapshots · JSON
9 +2 netblocks since 2026-07-05
2026-07-05 peak 9 2026-09-06

Network trust

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

These blocks are registered to TAG Systems but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

168.205.64.0/24 /24 authorized for AS16973 — AS16973

NIC Handles

AMP2 AMP2 AMP2 AMP2 AMP2 AMP2 AS16973 ATMAN-MNT CR-CRCH-LACNIC CR-CRCH-LACNIC DUMY-RIPE DUMY-RIPE +3 more