Autonomous system
AS216063 TWENTYFOURFIRE 24fire GmbH
Unclassified RIPE
Summary
24fire GmbH
business api germany
The AS handle TWENTYFOURFIRE is held by 24fire GmbH.
What it's used for
- The address space carries API and corporate endpoints, evidenced by reverse DNS entries for
fireapi.deand24fire.deacross multiple prefixes. - The network announces 2304 IPv4 addresses and 4 IPv6 prefixes, with only 3 observed neighbours, indicating a small-scale business or internal corporate estate rather than a transit or large access network.
- Traffic from this AS consists of web and API endpoints for the company's services, consistent with its role as a technology provider.
Notable
- All registrants in the RDAP data agree with the announcer, listing
24fire GmbHas the holder for all seven IPv4 prefixes. - The address inventory is finely subdivided into seven distinct IPv4 prefixes and four IPv6 prefixes, reflecting a segmented internal corporate estate.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| ERA-IX Frankfurt | Frankfurt, Germany | 185.0.27.89 |
Transit providers
3 upstream, 0 downstream and 6 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-01, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 7 prefixes · 2.30K addresses IPv6 4 prefixes
| Country | Name | Prefixes |
|---|---|---|
| DE | Germany | 11 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS216063- Registry name
- TWENTYFOURFIRE
- Registrant
- 24fire GmbH
- Abuse contact
- abuse@24fire-gmbh.de
- Registered
- 2023-10-31
- Last changed
- 2026-06-29
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- TWENTYFOURFIRE
- Scope
- Europe
- Traffic ratio
- Balanced
- Peering policy
- Open
- Facilities
- 2 facilities
- Website
- https://24fire.de/
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 79% valid · 11 valid, 3 with no ROA
- ROAs
- 8 authorising AS216063
- ASPA
- no ASPA record
- IRR
- 100% registered · 14 of 14 announcements
- Route objects
- 15 naming AS216063
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 447 networks and 1,843 prefixes, as published 2026-11-02. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere