BTC
BTC Ltd.
Data as of 2026-08-16
GLEIF verified
LEI
875500LGWJ80Z1O0CW18
Registered name
BTC
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
| Netblocks | 24 · 2,388 IPv4 addresses |
| IPv6 | 1 prefix (largest 2a03:5a00:38::/48) |
| Registered in | Bulgaria (7) · Saudi Arabia (3) · Russia (2) · Czechia (2) · United Kingdom (2) · Hong Kong (2) |
| All fragments | 233 blocks across 156 clusters |
| Cluster ID | 222467858 |
| Registry | APNIC |
| Owner jurisdiction | BE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | GLEIF legal-entity match |
| Legal identity | LEI 875500LGWJ80Z1O0CW18 |
| Shared handles | clustered on 30 shared RIR contact/maintainer handles |
| Registry names | 6 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
8 weekly snapshots · JSON
26
0 netblocks since 2026-07-05
2026-07-05
peak 26
2026-08-16
IP Ranges (24)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 93.170.82.0/24 | BTC Ltd. | RIPE | ASSIGNED PA | ● high |
| 123.127.107.240/28 | BTC | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 157.22.229.0/24 | BTC Ltd. | RIPE | ASSIGNED PI | ● high |
| 193.190.238.64/26 | BTC | RIPE | ASSIGNED PA | ● high |
| 2a03:5a00:38::/48 | BTC Ltd. | BGP | ANNOUNCED | ● high |
| 46.10.219.32/27 | BTC-NET | RIPE | ASSIGNED PA | ● low |
| 46.10.219.64/27 | BTC-NET | RIPE | ASSIGNED PA | ● low |
| 61.93.253.148/30 | BTC | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 78.138.211.80/29 | BTC | RIPE | ASSIGNED PA | ● low |
| 80.228.111.0/26 | BTC-AG-NET | RIPE | ASSIGNED PA | ● low |
| 85.128.60.176/29 | BTC | RIPE | ASSIGNED PA | ● low |
| 85.146.208.16/29 | BTC | RIPE | ASSIGNED PA | ● low |
| 94.126.47.128/25 | BTC-NET | RIPE | ASSIGNED PA | ● low |
| 94.236.146.0/24 | BTC | RIPE | ASSIGNED PA | ● low |
| 94.236.153.0/24 | BTC | RIPE | ASSIGNED PA | ● low |
| 94.236.154.0/24 | BTC | RIPE | ASSIGNED PA | ● low |
| 94.236.234.0/24 | BTC | RIPE | ASSIGNED PA | ● low |
| 94.236.235.0/24 | BTC | RIPE | ASSIGNED PA | ● low |
| 109.239.82.48/28 | BTC | RIPE | ASSIGNED PA | ● low |
| 203.186.222.32/28 | BTC | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 212.13.227.128/25 | BTC | RIPE | ASSIGNED PA | ● low |
| 212.63.210.168/29 | BTC-NET | RIPE | ASSIGNED PA | ● low |
| 212.107.101.32/27 | BTC | RIPE | ASSIGNED PA | ● low |
| 212.107.120.64/27 | BTC | RIPE | ASSIGNED PA | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2a03:5a00:38::/48 |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
88.5%
of checked blocks have valid RPKI ROA coverage
(23 of 26)
Possible discrepancies (5)
These blocks are registered to BTC Ltd. 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.
| 94.236.146.0/24 /24 | authorized for AS8866 — Vivacom Bulgaria EAD |
| 94.236.153.0/24 /24 | authorized for AS8866 — Vivacom Bulgaria EAD |
| 94.236.154.0/24 /24 | authorized for AS8866 — Vivacom Bulgaria EAD |
| 94.236.234.0/24 /24 | authorized for AS8866 — Vivacom Bulgaria EAD |
| 94.236.235.0/24 /24 | authorized for AS8866 — Vivacom Bulgaria EAD |
NIC Handles
AC2009-AP
AS62247
AS9119-MNT
BAC64-RIPE
BELNET-MNT
BT95-ADM
BTK-MNT
BTK-MNT
CH134-AP
DUMY-RIPE
DUMY-RIPE
EWETEL-MNT
+18 more