Skip to main content

AS197969

MARSAT-AS

Federal State Unitary Enterprise "Morsviazsputnik"

Registry

Authoritative registration data

AS number
197969
Name
MARSAT-AS
Organisation
Federal State Unitary Enterprise "Morsviazsputnik"
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 AS197969
149.62.160.0/21 IPv4 /21 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 AS197969 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS197969 in AS paths

Observed upstreams
Families
AS59692 104 140
v4
AS1299 TWELVE99 85 115
v4
AS51601 21 32
v4
AS6939 HURRICANE 21 22
v4
AS57724 DDOS-GUARD 11 11
v4
AS25091 IP-Max 5 9
v4
AS41327 FIBERTELECOM-AS 2 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS197969 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 3
v4
AS28910 1 1
v4
AS29049 1 1
v4
AS35598 1 1
v4
AS36236 NETACTUATE 1 1
v4
AS41722 1 1
v4
AS49673 TRUENETWORK 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.