Skip to main content

AS57174

SETISERVISY

ORG-NASJ1-RIPE

Registry

Authoritative registration data

AS number
57174
Name
SETISERVISY
Organisation
ORG-NASJ1-RIPE
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 AS57174
95.215.176.0/21 IPv4 /21 not checked
185.42.48.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

Internet Exchange memberships listed for AS57174
Address families
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS57174 in AS paths

Observed upstreams
Families
AS3216 SOVAM-AS 397 1,203
v4
AS35598 260 390
v4
AS20764 RASCOM-AS 171 327
v4
AS62255 BEMYLINK 174 275
v4
AS25091 IP-Max 16 90
v4
AS1299 TWELVE99 29 78
v4
AS25478 26 33
v4
AS9049 7 20
v4
AS9198 KAZTELECOM-AS 8 18
v4
AS8241 6 18
v4
AS137409 GSLNETWORKS-AS-AP 6 14
v4
AS50384 W-IX_LTD 5 6
v4
AS13194 BITE 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS57174 in AS paths

Observed downstreams
Families
AS209759 263 794
v4
AS8241 196 433
v4
AS39156 213 325
v4
AS202599 57 172
v4
AS47333 HighLink-spb-as 108 134
v4

No rows match “”.

Showing – of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 6 68
v4
AS37721 ORG-VTS1-AFRINIC 7 17
v4
AS49434 FBWNETWORKS 7 17
v4
AS49544 i3Dnet 5 12
v4
AS199524 GCORE 7 10
v4
AS41327 FIBERTELECOM-AS 3 4
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.