Skip to main content

AS198185

LIGALINK-AS

-------------------------------------------------------------

Registry

Authoritative registration data

AS number
198185
Name
LIGALINK-AS
Organisation
-------------------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS198185
130.255.8.0/21 IPv4 /21 not checked
2a00:4aa0::/32 IPv6 /32 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 AS198185
Address families
MSK-IX Moscow: MSK-IX peering network 10,000 Mbps IPv4
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 AS198185 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS198185 in AS paths

Observed upstreams
Families
AS50509 TRANSROUTE 412 804
v4
AS199624 DKTEL-AS 386 649
v4 v6
AS25091 IP-Max 9 32
v4 v6
AS9198 KAZTELECOM-AS 2 4
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS198185 in AS paths

Observed downstreams
Families
AS204199 SURYA-AS 296 777
v4

No rows match “”.

Showing – of

Uncertain adjacencies

9 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 21
v4 v6
AS36236 NETACTUATE 2 4
v4 v6
AS41327 FIBERTELECOM-AS 2 4
v4 v6
AS41722 MIRAN-AS 2 4
v4 v6
AS37721 ORG-VTS1-AFRINIC 2 3
v4
AS49434 FBWNETWORKS 2 3
v4
AS49673 TRUENETWORK 2 3
v4
AS205112 PHILUNET 2 3
v4
AS28910 INTAL-ASN 1 1
v6

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.