Skip to main content

AS57317

SERVERMEILE-AS

Servermeile GmbH

Registry

Authoritative registration data

AS number
57317
Name
SERVERMEILE-AS
Organisation
Servermeile GmbH
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

3

Total announced

8

Announced prefixes

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

Prefixes announced by AS57317
185.105.112.0/24 IPv4 /24 not checked
185.105.113.0/24 IPv4 /24 not checked
185.105.114.0/24 IPv4 /24 not checked
185.105.115.0/24 IPv4 /24 not checked
185.134.242.0/24 IPv4 /24 not checked
2a06:3700:10::/44 IPv6 /44 not checked
2a06:3700::/44 IPv6 /44 not checked
2a06:3707:f000::/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 AS57317
Address families
BCIX: BCIX Peering LAN 20,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 AS57317 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS57317 in AS paths

Observed upstreams
Families
AS5405 252 2,166
v4 v6
AS6939 HURRICANE 59 278
v4 v6
AS3320 DTAG 29 195
v4 v6
AS9002 RETN-AS 6 30
v6
AS24961 2 16
v4 v6
AS6797 GLOBALCONNECT-NET 1 16
v4 v6
AS39351 ESAB-AS 2 13
v4 v6
AS33891 CORE-BACKBONE 1 5
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS57317 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
AS8218 NEO-ASN 1 56
v4 v6
AS24482 SGGS-AS-AP 1 38
v4 v6
AS680 1 8
v4 v6
AS50629 LWLCOM 1 8
v4 v6
AS13237 LAMBDANET-AS 1 5
v4

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.