BITEMOBILE-LV
BGP inherited
Cluster stats
| Netblocks | 18 · 12,270 IPv4 addresses |
| Registered in | LV (14) · LT (4) |
| Cluster ID | 209305006 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 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
17
0 netblocks since 2026-07-05
2026-07-05
peak 17
2026-07-19
IP Ranges (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 84.15.136.0/21 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 84.15.192.0/22 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 84.15.208.0/20 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 85.254.69.0/24 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 85.254.71.0/24 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 85.254.102.0/24 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 85.254.123.0/24 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 85.254.149.0/24 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 85.254.151.0/24 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 85.254.152.0/22 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 85.254.170.0/24 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 85.254.176.0/23 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 91.190.45.0/24 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 91.190.48.0/24 | BITEMOBILE-LV | RIPE | ASSIGNED PA | ● low |
| 91.190.49.0/24 | BITEMOBILE-LV | RIPE | SUB-ALLOCATED PA | ● low |
| 159.148.73.0/24 | BITEMOBILE-LV | RIPE | LEGACY | ● low |
| 159.148.249.0/24 | BITEMOBILE-LV | RIPE | LEGACY | ● low |
| 213.226.140.0/23 | BITEMOBILE-LV | 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
(18 of 18)
RPKI-inferred operator
UAB "Bite Lietuva"
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
AS2588-MNT
BITE-NOC
BITE2000-RIPE
DUMY-RIPE
DUMY-RIPE
LATNET-MNT
SNLV-MNT