Country
—
ASN LANDING PAGE
TKPSA-AS P4 Sp. z o.o.
Last updated · Jul 20, 2026
Country
—
Total prefixes
59
IPv4 prefixes
57
IPv6 prefixes
2
TKPSA-AS P4 Sp. z o.o. currently reports 59 prefixes and 52 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.
TKPSA-AS P4 Sp. z o.o. 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.
AS199212
AS199212
—
AS39255
AS39255
—
AS198050
AS198050
—
AS28978
AS28978
—
AS43290
AS43290
—
AS33895
AS33895
—
AS28815
AS28815
—
AS47830
AS47830
—
AS48208
AS48208
—
AS197702
AS197702
—
AS198695
AS198695
—
AS198854
AS198854
—
AS201753
AS201753
—
AS212119
AS212119
—
AS34509
AS34509
—
AS34719
AS34719
—
AS60418
AS60418
—
AS203313
AS203313
—
AS205096
AS205096
—
AS212909
AS212909
—
AS12075
AS12075
—
AS197027
AS197027
—
AS43498
AS43498
—
AS198278
AS198278
—
AS12580
AS12580
—
AS49200
AS49200
—
AS198235
AS198235
—
AS52020
AS52020
—
AS49787
AS49787
—
AS45016
AS45016
—
AS31604
AS31604
—
AS19197
AS19197
—
AS35760
AS35760
—
AS198146
AS198146
—
AS39489
AS39489
—
AS207742
AS207742
—
AS197527
AS197527
—
AS199444
AS199444
—
AS44124
AS44124
—
AS44860
AS44860
—
| Prefix | Name | Country |
|---|---|---|
| 119.12.17.0/24 | AS31242 | — |
| 119.12.22.0/24 | AS31242 | — |
| 119.12.23.0/24 | AS31242 | — |
| 119.12.28.0/22 | AS31242 | — |
| 178.219.20.0/24 | AS31242 | — |
| 178.219.21.0/24 | AS31242 | — |
| 178.219.22.0/24 | AS31242 | — |
| 178.219.23.0/24 | AS31242 | — |
| 178.219.24.0/24 | AS31242 | — |
| 178.219.31.0/24 | AS31242 | — |
| 185.157.236.0/24 | AS31242 | — |
| 185.157.237.0/24 | AS31242 | — |
| 185.157.238.0/24 | AS31242 | — |
| 185.157.239.0/24 | AS31242 | — |
| 185.54.184.0/22 | AS31242 | — |
| 188.117.128.0/18 | AS31242 | — |
| 192.150.83.0/24 | AS31242 | — |
| 193.106.244.0/22 | AS31242 | — |
| 193.150.165.0/24 | AS31242 | — |
| 193.151.100.0/22 | AS31242 | — |
| 193.16.229.0/24 | AS31242 | — |
| 193.43.148.0/24 | AS31242 | — |
| 194.110.127.0/24 | AS31242 | — |
| 194.150.96.0/22 | AS31242 | — |
| 194.63.128.0/22 | AS31242 | — |
| 195.128.242.0/23 | AS31242 | — |
| 195.242.68.0/24 | AS31242 | — |
| 195.242.69.0/24 | AS31242 | — |
| 195.95.164.0/24 | AS31242 | — |
| 213.179.72.0/22 | AS31242 | — |
| 2a00:13a0::/32 | AS31242 | — |
| 2a10:ac00::/32 | AS31242 | — |
| 31.172.176.0/20 | AS31242 | — |
| 80.249.130.0/24 | AS31242 | — |
| 83.175.162.0/24 | AS31242 | — |
| 83.175.166.0/24 | AS31242 | — |
| 84.205.170.0/24 | AS31242 | — |
| 84.205.176.0/22 | AS31242 | — |
| 84.205.183.0/24 | AS31242 | — |
| 84.205.184.0/24 | AS31242 | — |
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.
AS31242 is an autonomous system number. The current source associates it with TKPSA-AS P4 Sp. z o.o. 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 AS31242. 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 AS31242, 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.