LRT
Unresolved
Cluster stats
| Netblocks | 2 |
| All fragments | 5 blocks across 4 clusters |
| Cluster ID | 193385676 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 77.241.206.76/32 | LRT | PEERINGDB | ASSIGNED | ● high |
| 185.216.211.0/24 | LRT | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to LRT 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.
| 185.216.211.0/24 /24 | authorized for AS209989 — UAB "Baltnetos komunikacijos" |
NIC Handles
AS209989
BNK-LT-MNT
DUMY-RIPE
DUMY-RIPE