Skip to main content

AS52043

TAIGET-AS

LLC "Multiservice"

Registry

Authoritative registration data

AS number
52043
Name
TAIGET-AS
Organisation
LLC "Multiservice"
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS52043
176.106.16.0/20 IPv4 /20 not checked
176.106.8.0/21 IPv4 /21 not checked
176.124.120.0/21 IPv4 /21 not checked
46.151.240.0/21 IPv4 /21 not checked
176.124.116.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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS52043 in AS paths

Observed upstreams
Families
AS31133 MF-MGSM-AS 80 455
v4
AS47586 Business-Svyaz 63 365
v4
AS6939 HURRICANE 11 55
v4
AS25091 IP-Max 2 10
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS52043 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 10
v4
AS49673 TRUENETWORK 1 5
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.