Country
—
ASN LANDING PAGE
TNS-Plus-Core TNS-Plus LLP
Last updated · Apr 10, 2026
Country
—
Total prefixes
8
IPv4 prefixes
7
IPv6 prefixes
1
TNS-Plus-Core TNS-Plus LLP currently shows 8 prefixes and 80 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.
ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.
TNS-Plus-Core TNS-Plus LLP is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.
This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.
Detailed data for this ASN is not available right now.
AS8449
AS8449
—
AS21299
AS21299
—
AS197556
AS197556
—
AS200590
AS200590
—
AS205516
AS205516
—
AS48503
AS48503
—
AS60757
AS60757
—
AS35104
AS35104
—
AS39824
AS39824
—
AS58172
AS58172
—
AS48716
AS48716
—
AS8393
AS8393
—
AS29046
AS29046
—
AS51878
AS51878
—
AS57008
AS57008
—
AS206026
AS206026
—
AS207446
AS207446
—
AS197686
AS197686
—
AS12997
AS12997
—
AS59443
AS59443
—
AS35566
AS35566
—
AS41329
AS41329
—
AS212999
AS212999
—
AS8200
AS8200
—
AS216384
AS216384
—
AS58289
AS58289
—
AS210273
AS210273
—
AS197968
AS197968
—
AS13335
AS13335
—
AS49070
AS49070
—
AS42770
AS42770
—
AS212675
AS212675
—
AS51162
AS51162
—
AS41124
AS41124
—
AS54994
AS54994
—
AS201153
AS201153
—
AS203481
AS203481
—
AS211002
AS211002
—
AS212013
AS212013
—
AS213048
AS213048
—
AS3216
AS3216
—
AS20485
AS20485
—
AS31133
AS31133
—
AS9002
AS9002
—
AS6939
AS6939
—
AS43727
AS43727
—
AS205103
AS205103
—
AS35104
AS35104
—
AS28910
AS28910
—
AS35280
AS35280
—
AS34549
AS34549
—
AS5405
AS5405
—
AS34019
AS34019
—
AS25091
AS25091
—
AS8758
AS8758
—
AS34927
AS34927
—
AS199524
AS199524
—
AS8298
AS8298
—
AS35625
AS35625
—
AS34177
AS34177
—
AS6057
AS6057
—
AS24961
AS24961
—
AS41327
AS41327
—
AS29691
AS29691
—
AS36236
AS36236
—
AS24482
AS24482
—
AS137409
AS137409
—
AS12779
AS12779
—
AS35360
AS35360
—
AS64475
AS64475
—
AS29075
AS29075
—
AS37100
AS37100
—
AS58299
AS58299
—
AS23764
AS23764
—
AS25160
AS25160
—
AS52320
AS52320
—
AS58057
AS58057
—
AS264479
AS264479
—
AS3214
AS3214
—
AS6424
AS6424
—
| Prefix | Name | Country |
|---|---|---|
| 2a01:68c0::/32 | AS35168 | — |
| 46.227.186.0/24 | AS35168 | — |
| 46.227.187.0/24 | AS35168 | — |
| 46.227.188.0/24 | AS35168 | — |
| 46.227.189.0/24 | AS35168 | — |
| 89.38.164.0/22 | AS35168 | — |
| 89.38.164.0/24 | AS35168 | — |
| 89.38.167.0/24 | AS35168 | — |
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
Useful when you want to compare this ASN against larger cloud and edge networks.
Continue from the ASN page into WHOIS and ownership verification.
AS35168 is an autonomous system number used to identify an independently operated network. The current page associates it with TNS-Plus-Core TNS-Plus LLP in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
They help explain the scale, interconnection depth, and route structure of AS35168. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS35168, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.