LVRTC Network
Cluster stats
Netblocks17
Cluster ID193383899
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (17)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.241.206.140/32 LVRTC Network PEERINGDB ASSIGNED ● high
185.1.236.10/32 LVRTC Network PEERINGDB ASSIGNED ● high
185.1.236.130/32 LVRTC Network PEERINGDB ASSIGNED ● high
192.121.80.25/32 LVRTC Network PEERINGDB ASSIGNED ● high
195.246.227.42/32 LVRTC Network PEERINGDB ASSIGNED ● high
195.246.227.170/32 LVRTC Network PEERINGDB ASSIGNED ● high
2001:7f8:16::8194:1/128 LVRTC Network PEERINGDB ASSIGNED ● high
2001:7f8:16::8194:2/128 LVRTC Network PEERINGDB ASSIGNED ● high
2001:7f8:3e:0:a500:0:8194:1/128 LVRTC Network PEERINGDB ASSIGNED ● high
2001:7f8:126::10/128 LVRTC Network PEERINGDB ASSIGNED ● high
2001:7f8:126::130/128 LVRTC Network PEERINGDB ASSIGNED ● high
2001:1ab8:8486::140/128 LVRTC Network PEERINGDB ASSIGNED ● high
195.244.158.0/24 LVRTC-EU RIPE ASSIGNED PA ● low
212.70.178.0/28 LVRTC-LV RIPE ASSIGNED PA ● low
212.70.190.72/30 LVRTC-LV RIPE ASSIGNED PA ● low
212.70.190.76/30 LVRTC-LV RIPE ASSIGNED PA ● low
2a00:1780::/48 LVRTC-LV RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: B how networks compare →
88.2% of checked blocks have valid RPKI ROA coverage (15 of 17)
Possible discrepancies (2)

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

2a00:1780::/48 /48 authorized for AS8194 — VAS "Latvijas Valsts radio un televizijas centrs"
195.244.158.0/24 /24 authorized for AS62220 — State Regional Development Agency

NIC Handles

AS8194 AS8194-MNT DUMY-RIPE DUMY-RIPE