Autonomous system
AS8804 REGIO-AS Bahnhofstr. 8, 36157 Ebersburg
Unclassified RIPE
Summary
regio[.NET] Holding GmbH
transit isp legacy
REGIO-AS is regio[.NET] Holding GmbH of Ebersburg, near Fulda in Hesse. The worklist handle appends the company's postal address (Bahnhofstr. 8, 36157 Ebersburg), so the raw string reads like a street rather than a network. regio.NET set up its first internet connection in February 1996, making it the first dedicated IP service provider in its region.
What it's used for
The evidence points at a backbone and interconnect role rather than a retail access network. The AS announces only ~3,300 IPv4 addresses across three prefixes, yet shows 131 observed BGP neighbours. A small address holding behind a large peer count is the signature of a network whose business is carrying traffic, not numbering subscribers. This matches the company's own history: after a 2002 restructuring it spun off parts of the business and from 2004 concentrated on backbone and consulting, separating from the local access segment.
Sampled reverse DNS supports that read:
lo0.core-gw1.ffm0.regio.net— a core router loopback,ffm0for Frankfurtcore-gw.ffm0.upstream.as— more interconnect gear
Notable
- One sampled address does return
dsl.regio.netnaming, a residue of the older regional access business. It is a minority of the sample and does not outweigh the router-heavy shape; the network today reads as carrier infrastructure with some legacy access space still attached. 192.135.7.0/24is a legacy assignment sitting alongside more recent94.137.152.0/21and193.238.196.0/22blocks, the usual patchwork of a long-lived small German operator.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Address space
Summary
| Country | Name | Prefixes |
|---|---|---|
| DE | Germany | 4 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS8804- Registry name
- REGIO-AS
- Registrant
- kroenung-mnt
- Abuse contact
- peering@regio.net
- Registered
- 1970-01-01
- Last changed
- 2019-02-08
- Status
- active
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
No IC3 indicators Nothing from the FBI IC3 feed.
Threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere