Country
—
ASN LANDING PAGE
Tschajera-Limited Tschajera Limited
Last updated · Jul 20, 2026
Country
—
Total prefixes
17
IPv4 prefixes
1
IPv6 prefixes
16
Tschajera-Limited Tschajera Limited currently reports 17 prefixes and 80 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
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.
Tschajera-Limited Tschajera Limited 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.
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.
Detailed data for this ASN is not available right now.
AS1299
AS1299
—
AS6939
AS6939
—
AS174
AS174
—
AS37468
AS37468
—
AS137409
AS137409
—
AS34927
AS34927
—
AS33891
AS33891
—
AS64049
AS64049
—
AS20485
AS20485
—
AS31133
AS31133
—
AS57463
AS57463
—
AS37100
AS37100
—
AS50263
AS50263
—
AS7713
AS7713
—
AS23764
AS23764
—
AS212895
AS212895
—
AS50673
AS50673
—
AS8881
AS8881
—
AS37662
AS37662
—
AS44592
AS44592
—
AS50629
AS50629
—
AS4651
AS4651
—
AS209718
AS209718
—
AS204438
AS204438
—
AS214006
AS214006
—
AS52025
AS52025
—
AS41051
AS41051
—
AS6204
AS6204
—
AS29632
AS29632
—
AS200586
AS200586
—
AS39386
AS39386
—
AS24785
AS24785
—
AS24482
AS24482
—
AS56655
AS56655
—
AS8218
AS8218
—
AS1680
AS1680
—
AS215223
AS215223
—
AS12741
AS12741
—
AS3326
AS3326
—
AS149476
AS149476
—
AS209718
AS209718
—
AS34927
AS34927
—
AS6939
AS6939
—
AS1299
AS1299
—
AS174
AS174
—
AS14907
AS14907
—
AS29632
AS29632
—
AS8218
AS8218
—
AS34019
AS34019
—
AS29075
AS29075
—
AS25091
AS25091
—
AS212483
AS212483
—
AS1140
AS1140
—
AS3333
AS3333
—
AS12859
AS12859
—
AS56987
AS56987
—
AS204092
AS204092
—
AS209090
AS209090
—
AS20932
AS20932
—
AS33891
AS33891
—
AS42541
AS42541
—
AS45489
AS45489
—
AS49544
AS49544
—
AS62167
AS62167
—
AS64475
AS64475
—
AS205112
AS205112
—
AS8298
AS8298
—
AS17639
AS17639
—
AS50869
AS50869
—
AS51185
AS51185
—
AS37468
AS37468
—
AS41666
AS41666
—
AS50673
AS50673
—
AS60326
AS60326
—
AS14840
AS14840
—
AS20485
AS20485
—
AS37100
AS37100
—
AS39351
AS39351
—
AS41051
AS41051
—
AS47498
AS47498
—
| Prefix | Name | Country |
|---|---|---|
| 143.246.143.0/24 | AS209022 | — |
| 2a07:54c4:174e::/48 | AS209022 | — |
| 2a0c:9a40:8c40::/48 | AS209022 | — |
| 2a0c:9a40:c000::/36 | AS209022 | — |
| 2a0c:9a40:c000::/48 | AS209022 | — |
| 2a0c:9a40:c001::/48 | AS209022 | — |
| 2a0c:9a40:c003::/48 | AS209022 | — |
| 2a0c:9a40:c005::/48 | AS209022 | — |
| 2a0c:9a40:c009::/48 | AS209022 | — |
| 2a10:a500:b00b::/48 | AS209022 | — |
| 2a10:a501:b00b::/48 | AS209022 | — |
| 2a10:a502:b00b::/48 | AS209022 | — |
| 2a10:a503:b00b::/48 | AS209022 | — |
| 2a10:a504:b00b::/48 | AS209022 | — |
| 2a10:a505:b00b::/48 | AS209022 | — |
| 2a10:a506:b00b::/48 | AS209022 | — |
| 2a10:a507:b00b::/48 | AS209022 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS209022 is an autonomous system number. The current source associates it with Tschajera-Limited Tschajera Limited and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS209022. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS209022, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.