BTC-Mobile
BGP inherited
Cluster stats
| Netblocks | 2 · 286 IPv4 addresses |
| All fragments | 3 blocks across 2 clusters |
| Cluster ID | 210506725 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 83.228.109.0/24 | BTC-Mobile | RIPE | ASSIGNED PA | ● low |
| 213.91.139.96/27 | BTC-Mobile | 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 BTC-Mobile 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.
| 83.228.109.0/24 /24 | authorized for AS8866 — Vivacom Bulgaria EAD |
NIC Handles
BT95-ADM
DUMY-RIPE
DUMY-RIPE