Skip to main content

AS62040

ITK-AS

---------Uplinks---------

Registry

Authoritative registration data

AS number
62040
Name
ITK-AS
Organisation
---------Uplinks---------
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 AS62040
185.14.4.0/24 IPv4 /24 not checked
185.49.240.0/24 IPv4 /24 not checked
185.49.241.0/24 IPv4 /24 not checked
185.49.242.0/24 IPv4 /24 not checked
185.49.243.0/24 IPv4 /24 not checked
186.246.42.0/24 IPv4 /24 not checked
186.246.43.0/24 IPv4 /24 not checked
193.176.80.0/24 IPv4 /24 not checked
193.176.83.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 AS62040
Address families
GNM-IX 100,000 Mbps IPv4 · IPv6
PITER-IX Helsinki 100,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 200,000 Mbps IPv4 · IPv6
PITER-IX Riga: RIX_PEERING_VLAN 200,000 Mbps IPv4
PITER-IX Rostov 200,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 200,000 Mbps IPv4 · IPv6

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

Source:ripestat:asn-neighbours observed

Observed upstreams

21 networks seen before AS62040 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS62040 in AS paths

Observed downstreams
Families
AS60365 IPCOM-AS 255 469
v4

No rows match “”.

Showing – of

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.