Country
—
ASN LANDING PAGE
AS204861
CODISATS Codisa Telco Solutions S.L.
Last updated · Jul 20, 2026
Total prefixes
5
IPv4 prefixes
4
IPv6 prefixes
1
ASN summary
How to read the scale of AS204861
CODISATS Codisa Telco Solutions S.L. currently reports 5 prefixes and 31 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?
CODISATS Codisa Telco Solutions S.L. 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 AS204861 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
AS204861 ASN lookupAS204861 BGPAS204861 peersAS204861 prefixesAS204861 upstreamsCODISATS Codisa Telco Solutions S.L. ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Peers
AS29119
AS29119
—
AS174
AS174
—
AS6939
AS6939
—
AS13030
AS13030
—
AS25091
AS25091
—
AS34549
AS34549
—
AS5405
AS5405
—
AS33891
AS33891
—
AS4230
AS4230
—
AS34927
AS34927
—
AS137409
AS137409
—
AS6057
AS6057
—
AS6424
AS6424
—
AS24482
AS24482
—
AS37680
AS37680
—
AS37721
AS37721
—
AS49544
AS49544
—
AS209823
AS209823
—
AS36236
AS36236
—
AS56987
AS56987
—
AS35280
AS35280
—
AS4455
AS4455
—
AS9009
AS9009
—
AS15704
AS15704
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 185.121.106.0/23 | AS204861 | — |
| 185.237.172.0/24 | AS204861 | — |
| 185.237.175.0/24 | AS204861 | — |
| 2.57.4.0/22 | AS204861 | — |
| 2a0c:1a80::/29 | AS204861 | — |
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 AS204861 represent?
AS204861 is an autonomous system number. The current source associates it with CODISATS Codisa Telco Solutions S.L. 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 AS204861 page?
They help explain the scale, interconnection depth, and route structure of AS204861. 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 AS204861?
Open a concrete IP page to check how the address maps into AS204861, 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.