ASN LANDING PAGE

AS206090

CYBERPUNK-AUTONOMOUS-SYSTEM Tomasz Plachecki

Last updated · Jul 20, 2026

Country

Total prefixes

1

IPv4 prefixes

0

IPv6 prefixes

1

ASN summary

How to read the scale of AS206090

CYBERPUNK-AUTONOMOUS-SYSTEM Tomasz Plachecki currently reports 1 prefixes and 2 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?

CYBERPUNK-AUTONOMOUS-SYSTEM Tomasz Plachecki 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 AS206090 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

AS206090 ASN lookupAS206090 BGPAS206090 peersAS206090 prefixesAS206090 upstreamsCYBERPUNK-AUTONOMOUS-SYSTEM Tomasz Plachecki ASN

Upstreams

Detailed data for this ASN is not available right now.

Downstreams

Detailed data for this ASN is not available right now.

Prefix inventory

PrefixNameCountry
2001:67c:1800::/48AS206090

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS206090 represent?

AS206090 is an autonomous system number. The current source associates it with CYBERPUNK-AUTONOMOUS-SYSTEM Tomasz Plachecki 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 AS206090 page?

They help explain the scale, interconnection depth, and route structure of AS206090. 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 AS206090?

Open a concrete IP page to check how the address maps into AS206090, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.

Related topics