Skip to main content

AS39561

AS-REGRU

"Domain names registrar REG.RU", Ltd

Registry

Authoritative registration data

AS number
39561
Name
AS-REGRU
Organisation
"Domain names registrar REG.RU", 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 AS39561
194.67.73.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 AS39561 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS39561 in AS paths

Observed upstreams
Families
AS202984 team-host 373 16,106
v4
AS57724 DDOS-GUARD 431 6,802
v4 v6
AS59692 IQWEB 621 4,179
v4 v6
AS6939 HURRICANE 44 1,774
v4
AS59796 STORMWALL-AS 443 1,516
v4
AS39134 UNITEDNET 73 1,484
v4 v6
AS201706 AS-SERVICEPIPE 306 1,392
v4
AS43298 StormNetworks 218 729
v4
AS25091 IP-Max 9 357
v4

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS39561 in AS paths

Observed downstreams
Families
AS197695 AS-REGRU 1,252 28,219
v4 v6
AS49352 LOGOL-AS 627 4,938
v4 v6
AS5537 RU-CENTER-AS 359 1,207
v4
AS205952 RUSONYX-AERO 143 167
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 238
v4
AS49673 TRUENETWORK 4 121
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.