Autonomous system
AS208709 APRIL-AS April Faye John
Unclassified RIPE Content
Summary
Servfail
content ipv6 germany
APRIL-AS is held by April Faye John, also known as Servfail.
What it's used for
- The address space carries content, as indicated by the PeeringDB information type and the operator's alias
Servfail. - The AS announces 2 IPv6 prefixes and 0 IPv4 addresses, with 10 observed neighbours.
- Traffic from this AS consists of content delivery or hosting services, consistent with the
Servfailbranding and content classification.
Notable
- The registry holder
April Faye Johnmatches the PeeringDB registrant, confirming identity alignment. - The address inventory consists solely of two /48 IPv6 blocks, with no IPv4 presence.
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 2 exchanges in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| KleyReX Internet Exchange | Frankfurt, Germany | 193.189.83.12 |
| Local Internet Exchange Düsseldorf | Düsseldorf, Germany | 185.1.155.192 |
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 0 prefixes · 0 addresses IPv6 2 prefixes
| Country | Name | Prefixes |
|---|---|---|
| DE | Germany | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS208709- Registry name
- APRIL-AS
- Registrant
- APRL-MNT
- Abuse contact
- aprl@linux.com
- Registered
- 2025-05-12
- Last changed
- 2025-11-27
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- April Faye John
- Also known as
- Servfail
- Network type
- Content
- Peering policy
- Open
- IRR as-set
RIPE::AS208709:AS-SERVFAIL- Present at
- 5 exchanges
- Website
- https://beta.servfail.network
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
- 0% valid · 0 valid, 2 with no ROA
- ROAs
- 2 authorising AS208709
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 4 naming AS208709
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