Skip to main content

AS61976

SELECTEL-NSK

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

Registry

Authoritative registration data

AS number
61976
Name
SELECTEL-NSK
Organisation
---------------------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

1

Total announced

11

Announced prefixes

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

Prefixes announced by AS61976
79.141.64.0/20 IPv4 /20 not checked
109.172.96.0/22 IPv4 /22 not checked
111.88.172.0/22 IPv4 /22 not checked
130.49.208.0/22 IPv4 /22 not checked
185.42.164.0/22 IPv4 /22 not checked
136.234.124.0/23 IPv4 /23 not checked
185.193.90.0/23 IPv4 /23 not checked
92.242.62.0/23 IPv4 /23 not checked
92.255.62.0/23 IPv4 /23 not checked
185.193.90.0/24 IPv4 /24 not checked
2a00:ab00:6000::/36 IPv6 /36 RPKI valid

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS61976 in AS paths

Observed upstreams
Families
AS20485 TRANSTELECOM 240 2,239
v4 v6
AS210756 EdgeCenterLLC 166 1,481
v4 v6
AS48858 Milecom-as 66 139
v4 v6
AS25091 IP-Max 4 75
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS61976 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49673 TRUENETWORK 1 10
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.