Skip to main content

AS206676

NDIX-TRANSIT

Nederlands-Duitse Internet Exchange B.V.

Registry

Authoritative registration data

AS number
206676
Name
NDIX-TRANSIT
Organisation
Nederlands-Duitse Internet Exchange B.V.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

0

Total announced

0

Announced prefixes

No announced prefixes observed

Route collectors saw no announcements from this AS, or the routing data source was unavailable.

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS206676 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS206676 in AS paths

Observed upstreams
Families
AS39686 AS-EUROFIBER 8 19
v6
AS8298 IPNG 6 11
v4 v6
AS1103 SURFNET-NL 3 7
v4 v6
AS6663 TTI-NET 2 5
v4 v6

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS206676 in AS paths

Observed downstreams
Families
AS16243 VIRTU-AS 21 83
v4 v6
AS202022 9 14
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

9 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 25
v4 v6
AS12779 ITGATE 1 8
v6
AS50763 MCKAYCOM 2 7
v4 v6
AS12859 NL-BIT 2 6
v6
AS202022 1 4
v4 v6
AS37721 ORG-VTS1-AFRINIC 2 3
v4 v6
AS213241 TECHIT 2 3
v6
AS16243 VIRTU-AS 1 3
v4 v6
AS36236 NETACTUATE 1 3
v4 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.