Country
—
ASN LANDING PAGE
AS48500
IRPNET-AS Irpinia Net-Com SRL
Last updated · Jul 20, 2026
Total prefixes
7
IPv4 prefixes
7
IPv6 prefixes
0
ASN summary
How to read the scale of AS48500
IRPNET-AS Irpinia Net-Com SRL currently reports 7 prefixes and 26 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
What can an ASN page answer?
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
How should you read the organization and region fields?
IRPNET-AS Irpinia Net-Com SRL is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
How should you verify the AS48500 result?
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
How to verify this ASN result
AS48500 ASN lookupAS48500 BGPAS48500 peersAS48500 prefixesAS48500 upstreamsIRPNET-AS Irpinia Net-Com SRL ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Peers
AS6939
AS6939
—
AS174
AS174
—
AS8218
AS8218
—
AS5405
AS5405
—
AS8660
AS8660
—
AS12637
AS12637
—
AS12779
AS12779
—
AS13237
AS13237
—
AS15605
AS15605
—
AS20912
AS20912
—
AS24482
AS24482
—
AS24961
AS24961
—
AS49544
AS49544
—
AS49605
AS49605
—
AS50877
AS50877
—
AS51185
AS51185
—
AS57111
AS57111
—
AS59919
AS59919
—
AS60171
AS60171
—
AS6204
AS6204
—
AS137409
AS137409
—
AS199039
AS199039
—
AS206952
AS206952
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 109.104.224.0/21 | AS48500 | — |
| 134.90.224.0/20 | AS48500 | — |
| 185.46.100.0/22 | AS48500 | — |
| 217.196.128.0/21 | AS48500 | — |
| 217.196.140.0/23 | AS48500 | — |
| 37.99.224.0/20 | AS48500 | — |
| 94.230.64.0/21 | AS48500 | — |
Related ASN pages
AS15169 · Google
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
AS13335 · Cloudflare
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
AS8075 · Microsoft
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
AS16509 · Amazon
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
Related lookups and next steps
Frequently asked questions about this ASN page
What does AS48500 represent?
AS48500 is an autonomous system number. The current source associates it with IRPNET-AS Irpinia Net-Com SRL and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
What are peers, upstreams, and prefixes useful for on the AS48500 page?
They help explain the scale, interconnection depth, and route structure of AS48500. 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 AS48500?
Open a concrete IP page to check how the address maps into AS48500, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Related topics
BGP and ASN Basics Guide
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Routing Troubleshooting and Network Analysis
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Cloud Network and ASN Comparison
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.