Skip to main content

AS42277

KURSKTELECOM-AS

CUSTOMERS:

Registry

Authoritative registration data

AS number
42277
Name
KURSKTELECOM-AS
Organisation
CUSTOMERS:
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

0

Total announced

9

Announced prefixes

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

Prefixes announced by AS42277
46.62.0.0/17 IPv4 /17 not checked
37.188.0.0/18 IPv4 /18 not checked
176.241.192.0/19 IPv4 /19 not checked
5.249.192.0/19 IPv4 /19 not checked
176.241.208.0/20 IPv4 /20 not checked
178.249.240.0/21 IPv4 /21 not checked
77.241.16.0/21 IPv4 /21 not checked
94.247.248.0/22 IPv4 /22 not checked
94.247.252.0/22 IPv4 /22 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 AS42277 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS42277 in AS paths

Observed upstreams
Families
AS8359 MTS 135 1,500
v4
AS12389 ROSTELECOM-AS 108 1,142
v4
AS25091 IP-Max 5 16
v4
AS209141 CMI-Russia 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS42277 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

9 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 6
v4
AS20764 RASCOM-AS 1 2
v4
AS28910 INTAL-ASN 1 2
v4
AS28917 Fiord-AS 1 2
v4
AS35598 INETCOM 1 2
v4
AS36236 NETACTUATE 1 2
v4
AS41327 FIBERTELECOM-AS 1 2
v4
AS41722 MIRAN-AS 1 2
v4
AS49673 TRUENETWORK 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.