Skip to main content

AS60359

ROZVYTOK-AS

---------------------- Upstreams ---------------------------

Registry

Authoritative registration data

AS number
60359
Name
ROZVYTOK-AS
Organisation
---------------------- Upstreams ---------------------------
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 AS60359
80.78.63.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 AS60359 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS60359 in AS paths

Observed upstreams
Families
AS25372 ITCONSULTING-AS 234 299
v4
AS6939 HURRICANE 18 20
v4
AS3303 SWISSCOM 8 11
v4
AS14840 ASN14840 2 5
v4
AS6663 TTI-NET 1 1
v4
AS263444 ASN263444 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS60359 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 2
v4
AS212483 level86 1 2
v4
AS48919 UA-CITY-AS 1 1
v4
AS198150 SIACOM-AS 1 1
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.