Skip to main content

AS201623

DUTCHELLIE-AS

--- Upstreams ---

Registry

Authoritative registration data

AS number
201623
Name
DUTCHELLIE-AS
Organisation
--- Upstreams ---
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

1

Total announced

1

Announced prefixes

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

Prefixes announced by AS201623
2001:678:ac4::/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 AS201623
Address families
FogIXP 1,000 Mbps IPv6
ixFabric - Amsterdam 1,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 AS201623 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS201623 in AS paths

Observed upstreams
Families
AS212635 AS212635 190 256
v6
AS34927 iFog-GmbH 52 69
v6
AS14840 ASN14840 2 5
v6
AS39351 ESAB-AS 2 2
v6
AS12735 ASTurkNet 1 2
v6
AS205794 RTTW-AS 1 1
v6
AS209022 Tschajera-Limited 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS201623 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
AS8298 IPNG 1 1
v6
AS41666 PYRO-AS 1 1
v6
AS60326 DEADBEEF-AS 1 1
v6
AS198150 SIACOM-AS 1 1
v6
AS209823 ENKI-AS 1 1
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.