Skip to main content

AS212781

Hypercon

Hypercon Ltd

Registry

Authoritative registration data

AS number
212781
Name
Hypercon
Organisation
Hypercon Ltd
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS212781
185.107.64.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 AS212781
Address families
GNM-IX 10,000 Mbps IPv4 · IPv6
THINX Warsaw 10,000 Mbps IPv4
TPIX PL 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 AS212781 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

14 networks seen before AS212781 in AS paths

Observed upstreams
Families
AS29535 191 253
v4
AS12741 48 50
v4
AS24724 14 20
v4
AS9002 RETN-AS 10 14
v4
AS8218 NEO-ASN 5 13
v4
AS9141 AS9141 10 10
v4
AS47692 NESSUS 2 4
v4
AS39351 ESAB-AS 2 2
v4
AS6204 1 1
v4
AS6663 TTI-NET 1 1
v4
AS9198 KAZTELECOM-AS 1 1
v4
AS15958 CETIN_doo_AS 1 1
v4
AS42295 TBISS-AS 1 1
v4
AS60171 AFRIX-AS 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS212781 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

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.