DEBACOM
BGP inherited
Cluster stats
| Netblocks | 9 · 6,142 IPv4 addresses |
| All fragments | 14 blocks across 3 clusters |
| Cluster ID | 208806433 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
9
0 netblocks since 2026-07-05
2026-07-05
peak 9
2026-07-19
IP Ranges (9)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 89.46.146.44/32 | DEBACOM | PEERINGDB | ASSIGNED | ● high |
| 178.212.40.0/21 | DEBACOM | RIPE | ASSIGNED PI | ● high |
| 178.215.192.0/20 | DEBACOM | RIPE | ASSIGNED PI | ● high |
| 178.216.40.25/32 | DEBACOM | PEERINGDB | ASSIGNED | ● high |
| 195.149.234.13/32 | DEBACOM | PEERINGDB | ASSIGNED | ● high |
| 2001:678:3ac::701/128 | DEBACOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:27::5:1337:1/128 | DEBACOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:5b::25/128 | DEBACOM | PEERINGDB | ASSIGNED | ● high |
| 2a02:c47:1c::/48 | DEBACOM | RIPE | AGGREGATED-BY-LIR | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “DEBACOM” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- DEBACOM Sp. z o.o. 3 blocks
- DEBACOM-ZABRZE 2 blocks
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(6 of 9)
No discrepancies found among checked blocks.
NIC Handles
AS51337
DUMY-RIPE
DUMY-RIPE
LEON-MNT
MNT-DEBACOM
ORG-DSzo11-RIPE
RIPE-NCC-END-MNT