Skip to main content

AS51942

EKMEDIA

======= TRANSIT ========

Registry

Authoritative registration data

AS number
51942
Name
EKMEDIA
Organisation
======= TRANSIT ========
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS51942
185.133.36.0/22 IPv4 /22 not checked
188.227.204.0/22 IPv4 /22 not checked
81.173.44.0/22 IPv4 /22 not checked
195.88.202.0/23 IPv4 /23 not checked
91.221.150.0/23 IPv4 /23 not checked
195.69.225.0/24 IPv4 /24 not checked
91.235.174.0/24 IPv4 /24 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 AS51942
Address families
ERA-IX Amsterdam 10,000 Mbps IPv4 · IPv6
INTERIX 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 AS51942 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

23 networks seen before AS51942 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS51942 in AS paths

Observed downstreams
Families
AS202796 JSR-IT-BV 124 702
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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