Skip to main content

AS39201

wavecom

WaveCom Informatikai Kft.

Registry

Authoritative registration data

AS number
39201
Name
wavecom
Organisation
WaveCom Informatikai Kft.
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 AS39201
185.152.180.0/24 IPv4 /24 RPKI valid
185.152.181.0/24 IPv4 /24 not checked
185.152.182.0/24 IPv4 /24 not checked
185.152.183.0/24 IPv4 /24 RPKI valid
45.128.69.0/24 IPv4 /24 not checked
45.128.70.0/24 IPv4 /24 RPKI valid
45.128.71.0/24 IPv4 /24 not checked
84.38.244.0/24 IPv4 /24 RPKI valid
2a0b:e5c0::/29 IPv6 /29 RPKI valid

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 AS39201
Address families
BIX 8,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 AS39201 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS39201 in AS paths

Observed upstreams
Families
AS29278 RACKHOST-HU-AS 1,287 3,965
v4 v6
AS44302 IECHU-AS 440 2,347
v4
AS6939 HURRICANE 67 81
v6
AS47692 NESSUS 2 36
v4 v6

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS39201 in AS paths

Observed downstreams
Families
AS208126 vinet_hu 416 1,384
v4 v6
AS203246 Mobillan-sat 323 876
v4 v6
AS204745 macronet 289 377
v4
AS213669 darksystems-as 277 373
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

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