Skip to main content

AS49925

STHNET-AS

LLC South Networks

Registry

Authoritative registration data

AS number
49925
Name
STHNET-AS
Organisation
LLC South Networks
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS49925
194.190.24.0/22 IPv4 /22 RPKI not found
194.190.24.0/24 IPv4 /24 RPKI not found
194.190.25.0/24 IPv4 /24 not checked
194.190.26.0/24 IPv4 /24 RPKI not found
194.190.27.0/24 IPv4 /24 not checked
194.226.111.0/24 IPv4 /24 not checked
195.208.108.0/24 IPv4 /24 RPKI not found

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 AS49925
Address families
PITER-IX Frankfurt 10,000 Mbps IPv4
PITER-IX Helsinki 10,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Riga: RIX_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Rostov 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Tallinn: TLL_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 AS49925 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS49925 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS49925 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS28910 INTAL-ASN 1 20
v4
AS37721 ORG-VTS1-AFRINIC 1 7
v4
AS41722 MIRAN-AS 1 7
v4
AS199524 GCORE 1 7
v4
AS205112 PHILUNET 1 7
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.