Skip to main content

AS215665

MARLONALKAN-AS

-------------------

Registry

Authoritative registration data

AS number
215665
Name
MARLONALKAN-AS
Organisation
-------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

3

Total announced

3

Announced prefixes

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

Prefixes announced by AS215665
2a07:54c1:4701::/48 IPv6 /48 not checked
2a07:54c1:4702::/48 IPv6 /48 not checked
2a07:54c1:4703::/48 IPv6 /48 not checked

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 AS215665
Address families
Frys-IX 10,000 Mbps IPv4 · IPv6
INTERIX 10,000 Mbps IPv4 · 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 AS215665 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS215665 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 174 722
v6
AS44854 45 222
v6
AS41051 21 84
v6
AS1103 SURFNET-NL 2 6
v6
AS56584 1 3
v6
AS401753 1 3
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS215665 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

12 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 9
v6
AS34019 HIVANE 1 9
v6
AS12859 1 6
v6
AS49544 i3Dnet 1 6
v6
AS3399 1 3
v6
AS5405 1 3
v6
AS24961 1 3
v6
AS29075 1 3
v6
AS39122 1 3
v6
AS209823 1 3
v6
AS212635 AS212635 1 3
v6
AS271253 1 3
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.