Skip to main content

AS60673

activcom

Activcom Kft.

Registry

Authoritative registration data

AS number
60673
Name
activcom
Organisation
Activcom Kft.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS60673
185.191.188.0/22 IPv4 /22 not checked
185.27.60.0/22 IPv4 /22 not checked
185.27.60.0/23 IPv4 /23 not checked
185.27.62.0/23 IPv4 /23 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 AS60673
Address families
BIX 10,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS60673 in AS paths

Observed upstreams
Families
AS41206 United-Telecom-HU-AS 209 530
v4
AS21334 ASN-ONE-HU 42 132
v4
AS6939 HURRICANE 42 98
v4
AS33891 CORE-BACKBONE 7 14
v4
AS47692 NESSUS 2 8
v4
AS6663 TTI-NET 1 2
v4
AS8447 A1TELEKOM-AT 1 2
v4
AS15958 CETIN_doo_AS 1 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS60673 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 4
v4
AS40994 Alwyzon 1 2
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.