Skip to main content

AS57537

NETDSIGN-AS

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

Registry

Authoritative registration data

AS number
57537
Name
NETDSIGN-AS
Organisation
===================================
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

1

Total announced

9

Announced prefixes

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

Prefixes announced by AS57537
213.148.96.0/19 IPv4 /19 not checked
185.152.232.0/22 IPv4 /22 not checked
185.152.232.0/24 IPv4 /24 not checked
185.152.233.0/24 IPv4 /24 not checked
185.152.234.0/24 IPv4 /24 not checked
185.152.235.0/24 IPv4 /24 not checked
213.148.98.0/24 IPv4 /24 not checked
213.148.99.0/24 IPv4 /24 not checked
2a03:2cc0::/32 IPv6 /32 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 AS57537
Address families
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 10,000 Mbps IPv4 · IPv6
DE-CIX Munich: DE-CIX Munich Peering LAN 10,000 Mbps IPv4 · IPv6
MegaIX Dusseldorf 1,000 Mbps IPv4 · IPv6
MegaIX Munich 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 AS57537 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

51 networks seen before AS57537 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS57537 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

53 adjacencies that may be an artefact of collector peering

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.