Skip to main content

AS207142

HMX

HMX Hungarian Media Exchange Kft

Registry

Authoritative registration data

AS number
207142
Name
HMX
Organisation
HMX Hungarian Media Exchange Kft
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

2

Total announced

4

Announced prefixes

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

Prefixes announced by AS207142
45.136.120.0/22 IPv4 /22 not checked
185.188.59.0/24 IPv4 /24 not checked
2a0e:9740::/29 IPv6 /29 RPKI not found
2a0b:b980:3::/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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS207142 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 359 1,101
v4 v6
AS6939 HURRICANE 70 187
v4 v6
AS47692 NESSUS 2 16
v4 v6
AS33891 CORE-BACKBONE 7 14
v4
AS6663 TTI-NET 1 2
v4
AS15958 CETIN_doo_AS 1 2
v4
AS21215 UGNI 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS207142 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 8
v4 v6
AS40994 Alwyzon 1 4
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.