Bulgartel
Cluster stats
| Netblocks | 12 |
| Cluster ID | 191666094 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (12)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.1.30.39/32 | Bulgartel | PEERINGDB | ASSIGNED | ● high |
| 185.1.137.152/32 | Bulgartel | PEERINGDB | ASSIGNED | ● high |
| 185.1.226.207/32 | Bulgartel | PEERINGDB | ASSIGNED | ● high |
| 193.25.181.1/32 | Bulgartel | PEERINGDB | ASSIGNED | ● high |
| 193.169.198.159/32 | Bulgartel | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:29f0::4:4814:1/128 | Bulgartel | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:63::1:1/128 | Bulgartel | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:db::4:4814:1/128 | Bulgartel | PEERINGDB | ASSIGNED | ● high |
| 95.169.209.0/24 | Bulgartel | RIPE | ASSIGNED PA | ● low |
| 95.169.219.0/24 | Bulgartel | RIPE | ASSIGNED PA | ● low |
| 195.34.102.0/27 | BULGARTEL | RIPE | ASSIGNED PA | ● low |
| 2a01:4a40:101::/48 | Bulgartel | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(9 of 12)
Possible discrepancies (2)
These blocks are registered to Bulgartel 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.
| 2a01:4a40:101::/48 /48 | authorized for AS214378 — MS Optic NET EOOD |
| 95.169.209.0/24 /24 | authorized for AS214378 — MS Optic NET EOOD |
NIC Handles
AS44814
BTEL-MNT
DUMY-RIPE
DUMY-RIPE
SPNET-MNT