Skip to main content

AS208709

APRIL-AS

=========================================

Registry

Authoritative registration data

AS number
208709
Name
APRIL-AS
Organisation
=========================================
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

2

Total announced

2

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS208709
2a0e:8f02:2031::/48 IPv6 /48 RPKI not found
2a0e:8f02:2038::/48 IPv6 /48 RPKI not found

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS208709
Address families
EVIX: Peering LAN 1,000 Mbps IPv6
KleyReX: Peering LAN 100 Mbps IPv6
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv4 · IPv6
WHY2025 IXP — IPv6
ixFabric - Dusseldorf 2,000 Mbps IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS208709 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS208709 in AS paths

Observed upstreams
Families
AS34872 Servperso_Systems 151 382
v6
AS212895 ROUTE64_ORG 75 180
v6
AS25091 IP-Max 3 12
v6
AS8298 IPNG 2 4
v6
AS211509 RUDAKI-AS 2 4
v6
AS401753 BIXCE 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS208709 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS34927 iFog-GmbH 1 2
v6
AS37989 DCS1PTELTD-AS-AP 1 2
v6
AS58057 SECUREBIT 1 2
v6
AS199854 ITBYPASSION 1 2
v6
AS403001 MIRAGE-GLOBAL-TECH 1 2
v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.