Skip to main content

AS51198

Servada

SERVADA

Registry

Authoritative registration data

AS number
51198
Name
Servada
Organisation
SERVADA
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

4

Total announced

9

Announced prefixes

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

Prefixes announced by AS51198
185.179.179.0/24 IPv4 /24 not checked
45.132.10.0/24 IPv4 /24 not checked
45.132.11.0/24 IPv4 /24 not checked
45.132.8.0/24 IPv4 /24 not checked
45.132.9.0/24 IPv4 /24 not checked
2a0e:6540::/29 IPv6 /29 not checked
2a0e:6542::/32 IPv6 /32 not checked
2a13:7d00::/32 IPv6 /32 not checked
2a13:7d01::/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 AS51198
Address families
ERA-IX Amsterdam 10,000 Mbps IPv4 · IPv6
ERA-IX Frankfurt 10,000 Mbps IPv4 · IPv6
Speed-IX: SPEED-IX 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 AS51198 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

25 networks seen before AS51198 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS51198 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

19 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.