Skip to main content

AS49359

RTSQUARE-AS

Dmitry Kozhushko

Registry

Authoritative registration data

AS number
49359
Name
RTSQUARE-AS
Organisation
Dmitry Kozhushko
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS49359
91.222.180.0/22 IPv4 /22 not checked
91.212.214.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 AS49359 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS49359 in AS paths

Observed upstreams
Families
AS48648 KYIVLINK 259 612
v4
AS6939 HURRICANE 21 46
v4
AS14840 ASN14840 2 10
v4
AS6663 TTI-NET 1 2
v4
AS263444 ASN263444 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS49359 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 16
v4
AS212483 level86 1 4
v4
AS48919 UA-CITY-AS 1 2
v4
AS59514 DARNYTSIA-NET 1 2
v4
AS198150 SIACOM-AS 1 2
v4
AS209823 ENKI-AS 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.