DTAG-HOTSPOT-KOELN-NET
BGP inherited
Cluster stats
| Netblocks | 10 |
| All fragments | 494 blocks across 187 clusters |
| Cluster ID | 210899224 |
| 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 | |
Footprint over time
5 weekly snapshots · JSON
10
0 netblocks since 2026-07-05
2026-07-05
peak 10
2026-07-19
IP Ranges (10)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 87.130.99.216/29 | DTAG-HOTSPOT-KOELN-NET | RIPE | ASSIGNED PA | ● low |
| 91.24.2.56/29 | DTAG-HOTSPOT-KOELN-NET | RIPE | ASSIGNED PA | ● low |
| 91.24.60.152/29 | DTAG-HOTSPOT-KOELN-NET | RIPE | ASSIGNED PA | ● low |
| 93.240.238.56/29 | DTAG-HOTSPOT-KOELN-NET | RIPE | ASSIGNED PA | ● low |
| 217.239.185.136/29 | DTAG-HOTSPOT-KOELN-NET | RIPE | ASSIGNED PA | ● low |
| 2003:c8:4832::/48 | DTAG-HOTSPOT-KOELN-NET | RIPE | ASSIGNED | ● low |
| 2003:ca:3825::/48 | DTAG-HOTSPOT-KOELN-NET | RIPE | ASSIGNED | ● low |
| 2003:ed:9028::/48 | DTAG-HOTSPOT-KOELN-NET | RIPE | ASSIGNED | ● low |
| 2003:f8:d013::/48 | DTAG-HOTSPOT-KOELN-NET | RIPE | ASSIGNED | ● low |
| 2003:fe:c02a::/48 | DTAG-HOTSPOT-KOELN-NET | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “DTAG HOTSPOT” — 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.
- DTAG-HOTSPOT-ERFURT-NET 16 blocks
- DTAG-HOTSPOT-FRANKFURT-AM-MAIN-NET 12 blocks
- DTAG-HOTSPOT-BERLIN-NET 12 blocks
- DTAG-HOTSPOT-HANNOVER-NET 11 blocks
- DTAG-HOTSPOT-WEIMAR-NET 10 blocks
- DTAG-HOTSPOT-NUERNBERG-NET 8 blocks
- DTAG-HOTSPOT-DUESSELDORF-NET 8 blocks
- DTAG-HOTSPOT-FRANKFURT-NET 6 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- DTAG-T-PUNKT-HOTSPOT-BIBERACH-NET via Deutsche Telekom AG sub-allocation
- DTAG-PROJEKT-HOTSPOT-M3-UECKERMUENDE-NET via Deutsche Telekom AG sub-allocation
- DTAG-T-PUNKT-HOTSPOT-DRESDEN-NET via Deutsche Telekom AG sub-allocation
- DTAG-PROJEKT-HOTSPOT-8857-MCDONALDS-VOEHRINGEN-NET via Deutsche Telekom AG sub-allocation
- DTAG-PROJEKT-HOTSPOT-8859-MCDONALDS-FLUGHAFEN-MUENCHEN-NET via Deutsche Telekom AG sub-allocation
- DTAG-HOTSPOT-NETHERLANDS via Deutsche Telekom AG sub-allocation
- DTAG-HOTSPOT-BELGIUM via Deutsche Telekom AG sub-allocation
- DTAG-PROJEKT-HOTSPOT-DB-8078-HBF-FRANKFURT-M-NET via Deutsche Telekom AG sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(10 of 10)
No discrepancies found among checked blocks.
NIC Handles
DTAG-NIC
DUMY-RIPE
DUMY-RIPE