Core Entity Brief
| Entity | 24fire GmbH |
|---|---|
| Public role | The provider matters because its prepaid credit model and single upstream dependency introduce a sharp failure mode: any disruption to its payment system, control panel, or transit connectivity can abruptly terminate customer services. With a company-reported base of over 5,000 customers, the platform represents a non-trivial, though unaudited, installed base. Its compact infrastructure footprint means that incidents at either of its two physical locations could cascade into widespread downtime. |
| Region | DE |
| Category | Digital infrastructure institution |
| Primary domain | Infrastructure |
| Signal focus | Institution Type |
| Time horizon | Quarter (30-120d) |
| Impact | Medium |
| Confidence | 0.85 |
| Evidence coverage | 11 public source references |
| Related coverage | Profile anchor article |
| Website | https://24fire.de/ |
| Last update | Jun 02, 2026 |
24fire GmbH is a German prepaid hosting provider and the operator of AS216063, offering KVM servers, domains, and webhosting from two data centres.
What It Does
- Visible operating role: 24fire GmbH sells prepaid KVM VPS, domains, webhosting, and storage through a self‑service control panel and FireAPI. All services are prepaid; once credit expires, servers are automatically stopped. The company operates its own ASN and peers at ERA‑IX Frankfurt, relying on a single upstream (AS49581).
- Revenue and customer gap: No public financial statements or audited customer‑count evidence exists. The company‑reported 5,000+ customers and 64 TB RAM are unaudited and cannot be verified from the provided sources.
Operating Snapshot
- Legal entity: 24fire GmbH, founded 4 July 2023, Amtsgericht Mannheim HRB 747763, capital €25,000. Address at Kronenstraße 4, 68723 Schwetzingen, Germany. Managing directors: Daniel Kuehn and Lars Kiefer. VAT ID DE362002832.
- Network footprint: AS216063 (TWENTYFOURFIRE), 6 IPv4 /24s, 3 IPv6 prefixes. Upstream: AS49581 (Tube‑Hosting). Peering at ERA‑IX Frankfurt. PeeringDB reports 5‑10 Gbps traffic and facilities at NTT Frankfurt 1 and SkyLink Data Center BV.
- Physical infrastructure: AMD EPYC and Ryzen clusters at NTT Frankfurt; Intel Xeon cluster at SkyLink Eygelshoven. Ceph‑based storage at Frankfurt. DDoS filtering combines an in‑house flowShield appliance at NTT and Aurologic protection at SkyLink.
- Service delivery: Customers manage services through a web control panel or FireAPI. API endpoints cover VMs, domains, DNS, backups, DDoS config, and status monitoring. Status page lists monitored components: Webshop, Control Panel, FireAPI, payment providers, network, DDoS protection, host systems, webhosting and storage.
Control Surface
- Platform controls: The control panel and FireAPI govern the lifecycle of KVM servers, domains, DNS, backups, and DDoS settings. The account‑credit system (including payment providers) and the status page are also part of the operational surface.
- Network controls: AS216063 prefixes, routing policies, and upstream/peering relationships control the flow of traffic to and from customer services. Changes can occur instantly and may not be immediately reflected in public datasets.
Watchpoints
- Record freshness: PeeringDB, RIPE DB, company register, or imprint changes would alter the operating picture. Check these sources close to publication.
- Infrastructure signals: Status‑page incidents, BGP prefix/upstream changes, DDoS‑filtering adjustments, or payment‑provider outages are the most direct indicators of platform stress.

