Skip to main content

AS39775

HYPERNET-AS

------------------------------------------------------------

Registry

Authoritative registration data

AS number
39775
Name
HYPERNET-AS
Organisation
------------------------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

0

Total announced

8

Announced prefixes

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

Prefixes announced by AS39775
62.192.32.0/19 IPv4 /19 not checked
81.90.208.0/20 IPv4 /20 not checked
185.190.0.0/22 IPv4 /22 not checked
91.204.16.0/22 IPv4 /22 not checked
185.149.126.0/24 IPv4 /24 not checked
62.192.32.0/24 IPv4 /24 not checked
81.90.208.0/24 IPv4 /24 not checked
81.90.221.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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS39775 in AS paths

Observed upstreams
Families
AS3216 SOVAM-AS 481 1,594
v4
AS9049 ERTH-TRANSIT-AS 350 939
v4
AS31133 MF-MGSM-AS 274 353
v4
AS47692 NESSUS 8 36
v4
AS50673 Serverius-as 11 23
v4
AS6939 HURRICANE 17 18
v4
AS39351 ESAB-AS 6 14
v4
AS41327 FIBERTELECOM-AS 4 10
v4
AS9198 KAZTELECOM-AS 4 7
v4
AS60171 AFRIX-AS 3 4
v4

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS39775 in AS paths

Observed downstreams
Families
AS41925 IZET-Chelyabinsk 346 552
v4
AS56436 62 79
v4
AS202835 60 75
v4

No rows match “”.

Showing of

Uncertain adjacencies

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