Country
—
ASN LANDING PAGE
AS47408
MANDARIN-AS - Mandarin S.p.A.
Last updated · Apr 4, 2026
Total prefixes
6
IPv4 prefixes
5
IPv6 prefixes
1
ASN summary
How to read the scale of AS47408
MANDARIN-AS - Mandarin S.p.A. currently shows 6 prefixes and 46 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.
When is an ASN page most useful?
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.
How should you read the country, organization, and role of AS47408?
MANDARIN-AS - Mandarin S.p.A. 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.
What should you inspect next after the AS47408 page?
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.
Search intents this ASN page helps cover
AS47408 ASN lookupAS47408 BGPAS47408 peersAS47408 prefixesAS47408 upstreamsMANDARIN-AS - Mandarin S.p.A. ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Peers
AS6939
AS6939
—
AS174
AS174
—
AS5405
AS5405
—
AS8218
AS8218
—
AS22356
AS22356
—
AS20811
AS20811
—
AS137409
AS137409
—
AS4455
AS4455
—
AS6762
AS6762
—
AS24961
AS24961
—
AS7713
AS7713
—
AS6204
AS6204
—
AS8660
AS8660
—
AS12637
AS12637
—
AS12779
AS12779
—
AS13237
AS13237
—
AS15605
AS15605
—
AS20912
AS20912
—
AS24482
AS24482
—
AS25160
AS25160
—
AS39120
AS39120
—
AS49544
AS49544
—
AS49605
AS49605
—
AS49709
AS49709
—
AS50877
AS50877
—
AS51185
AS51185
—
AS57111
AS57111
—
AS59919
AS59919
—
AS14840
AS14840
—
AS61973
AS61973
—
AS5392
AS5392
—
AS5394
AS5394
—
AS9009
AS9009
—
AS9498
AS9498
—
AS29049
AS29049
—
AS198150
AS198150
—
AS202032
AS202032
—
AS209234
AS209234
—
AS212483
AS212483
—
AS213315
AS213315
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 178.211.64.0/19 | AS47408 | — |
| 178.211.80.0/22 | AS47408 | — |
| 178.211.92.0/22 | AS47408 | — |
| 212.46.64.0/19 | AS47408 | — |
| 212.46.80.0/22 | AS47408 | — |
| 2a01:5f80::/32 | AS47408 | — |
Related ASN pages
AS15169 · Google
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
AS13335 · Cloudflare
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
AS8075 · Microsoft
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
AS16509 · Amazon
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Related lookups and next steps
WHOIS vs ASN Ownership Guide
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Routing Troubleshooting and Network Analysis
Continue from this ASN into route troubleshooting and network analysis.
Cloud Network and ASN Comparison
Useful when you want to compare this ASN against larger cloud and edge networks.
WHOIS and IP Ownership Guide
Continue from the ASN page into WHOIS and ownership verification.
Frequently asked questions about this ASN page
What does AS47408 represent?
AS47408 is an autonomous system number used to identify an independently operated network. The current page associates it with MANDARIN-AS - Mandarin S.p.A. in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
What are peers, upstreams, and prefixes useful for on the AS47408 page?
They help explain the scale, interconnection depth, and route structure of AS47408. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
What should you do after reviewing AS47408?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS47408, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Related topics
WHOIS vs ASN Ownership Guide
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
WHOIS and IP Ownership Guide
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
BGP and ASN Basics Guide
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Cloud Network and ASN Comparison
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.