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.
AutorJinny Xu
Editorial owner accountable for this profile route.
Tiempo de lectura4 min
Estimated reading time at standard editorial pace.
PublicadoMay 26, 2026
Date this profile last entered editorial circulation.
Last updateJun 02, 2026
Date this profile last entered editorial circulation.
CategoryDigital infrastructure institution
Controlled classification used for cross-profile comparison.
RegiónDE
Primary geography where current signals are most visible.
Signal FocusInstitution Type
Principal area tracked in this intelligence profile.
Tipo de contenidoProfile
Structured profile used for cross-category comparison.
Dominio principalInfrastructure
Primary editorial domain framing the analysis.
TemaInternet infrastructure
Controlled taxonomy label used for this profile route.
Horizonte temporalQuarter (30-120d)
Most likely window for material strategy effects.
ImpactoMediumThe signal alters planning assumptions but usually requires secondary implementation before full effect.
Confianza0.85
Anchored to multiple primary-source references and direct disclosures.
Paquete de evidencia
Fuentes primarias utilizadas para la clasificación y la puntuación de impacto.
24fire GmbH is a small German prepaid hosting provider operating AS216063 from two data centres. Its customers face service risk from prepaid credit expiry and single upstream dependence. Public evidence confirms corporate identity and network footprint but not financial health or operational control. Watchpoints include routing changes, director alterations, and status incidents. The profile is limited to source-backed claims with significant uncertainty about equipment ownership and management authority.
Core Entity Brief
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.
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.
Domain of operation
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.
Public role: 24fire GmbH is framed by 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. and public infrastructure context. Evidence basis: 24fire.de; 24fire.de
Operating surface: Internet infrastructure and DE provide the public context for this institution profile. Evidence basis: 24fire.de; 24fire.de
Timeline
24fire GmbH public profile updated
Public coverage records 24fire GmbH as a subject for role, operating context, and evidence review.
Signal Map
Signal Map
Why tracked: 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.
Object role: 24fire GmbH serves as a prepaid hosting provider and autonomous system operator in the German internet-infrastructure market. It manages the full lifecycle of customer KVM servers, domains, and web services through its in-house control panel and FireAPI. The company maintains its own network, AS216063, with announced IPv4 and IPv6 prefixes, and peers at ERA-IX Frankfurt. Its two data centres host AMD EPYC, Ryzen, and Intel Xeon clusters with Ceph storage and custom DDoS protection.
Impact note: If the control panel, FireAPI, payment providers, or DDoS filtering fail, customers may lose access to their virtual machines or be unable to renew. The dependency on a single upstream (AS49581) and two physical locations means that incidents at NTT Frankfurt or SkyLink Eygelshoven could degrade all services. Moreover, the prepaid model means that even a temporary payment issue can cause auto-shutdown after a grace period, leaving customers without recourse.
Control surface: public operating records, official service pages, source-backed relationship updates
Key dependencies: official company sources, public registries, operator-published records
Public View
The public read of 24fire GmbH is limited to visible role, operating context, and relationship evidence.
Watchpoints
New public role, affiliation, product, policy, or market disclosures.
Verified relationship changes involving named organizations or people.
Caveats
Private or unverified claims are excluded from this public view.
FAQ
Why is 24fire GmbH included?
24fire GmbH has public evidence that makes the institution relevant to BTW's coverage of digital infrastructure, governance, or markets.
What is public about this profile?
The public layer covers visible role, operating context, linked organizations, and evidence-backed watchpoints.
What should readers watch next?
Readers should watch for source-backed role changes, new partnerships, regulatory exposure, operating expansion, or evidence that changes the public assessment.
