Autonomous system
AS204818 HOSTEUR-NET-CORE Hosteur NETWORK CORE
Unclassified RIPE
Summary
Hosteur
hosting business france
HOSTEUR-NET-CORE is operated by Hosteur SAS.
What it's used for
- The address space carries hosting and business infrastructure, evidenced by netnames such as
FR-HOSTEUR-20090130,CH-7LXSERVICES-20190701, andHosteur-LILLE. - The AS announces 10,496 IPv4 addresses across 12 prefixes and 1 IPv6 prefix, with 9 observed neighbours, indicating a hosting or business provider role rather than a transit carrier.
- Traffic from this AS consists of web servers, API endpoints, and hosted services for business clients, consistent with Hosteur's role as a French hosting provider.
Notable
- Registrants include Hosteur SAS, 7LX SERVICES SARL, and CITYWAY SAS, with some prefixes showing different registrants than the announcer, suggesting leased space or post-acquisition history.
- The address inventory is fragmented across multiple /22 and /24 blocks, with some prefixes registered to third parties like 7LX SERVICES SARL and CITYWAY SAS.
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
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Transit providers
8 upstream, 1 downstream and 14 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-10-31, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 12 prefixes · 10.50K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| FR | France | 13 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS204818- Registry name
- HOSTEUR-NET-CORE
- Registrant
- MNT-ABCONNECT
- Abuse contact
- abuse-ripe@hosteur.com
- Registered
- 2018-01-02
- Last changed
- 2025-02-28
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- HOSTEUR
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
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
- 53% valid · 8 valid, 7 with no ROA
- ROAs
- 12 authorising AS204818
- ASPA
- no ASPA record
- IRR
- 100% registered · 15 of 15 announcements
- Route objects
- 20 naming AS204818
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,845 prefixes, as published 2026-10-31. 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