store.playstation.com Speed Test

Carrier
DNS

Nationwide Speed Map

Nationwide Speed Map
  • >10s
  • 3s-10s
  • 1s-3s
  • 0.5s-1s
  • <=0.5s
100%
RegionFastestSlowestAverage
All Nodes湖南邵阳移动 0.991s江西南昌移动 9.505s4.133s
China Telecom------
China Unicom------
China Mobile湖南邵阳移动 0.991s江西南昌移动 9.505s4.133s
East China浙江金华移动 2.957s江西南昌移动 9.505s4.465s
South China广东东莞移动 3.084s广西柳州移动 6.442s4.911s
Central China湖南邵阳移动 0.991s河南驻马店移动 9.229s4.606s
North China天津移动 1.152s 内蒙古包头移动 3.418s2.747s
Southwest四川成都移动 1.386s四川乐山移动 6.907s4.061s
Northwest甘肃庆阳移动 3.349s陕西渭南移动 4.309s3.712s
Northeast黑龙江鸡西移动 1.423s辽宁大连移动 3.272s2.562s
HK/MO/TW------

DNS Resolution Stats

7

Showing: 81/81

NodeResponse IPIP LocationStatusTotalResolveConnectDownloadRedirectHead
移动广东清远移动--保留Failed10.006s0.000s0.000s0.000s----
移动重庆江津移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2004.797s0.235s0.677s2.074s--
移动四川成都移动23.15.157.157新加坡/新加坡/新加坡/阿卡迈2001.386s0.006s0.262s0.853s--
移动安徽池州移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.357s0.214s0.613s1.205s--
移动湖南永州移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2008.662s0.158s1.643s3.047s--
移动广西贵港移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2006.154s0.543s1.614s2.088s--
移动安徽滁州移动--保留Failed0.007s0.000s0.000s0.000s----
移动内蒙古巴彦淖尔移动23.15.157.157新加坡/新加坡/新加坡/阿卡迈2002.998s0.016s1.317s0.891s--
移动江苏徐州移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.642s0.197s0.642s1.258s--
移动重庆沙坪坝移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.529s0.214s0.644s1.442s--
移动湖南长沙移动--保留Failed10.001s0.000s0.000s0.000s----
移动陕西西安2移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.812s0.212s0.631s1.887s--
移动重庆九龙坡移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.069s0.219s0.593s1.211s--
移动贵州贵阳移动--保留Failed10.001s0.000s0.000s0.000s----
移动福建漳州移动--保留Failed10.001s0.000s0.000s0.000s----
移动内蒙古呼和浩特移动--保留Failed10.001s0.000s0.000s0.000s----
移动北京移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.016s0.189s0.555s1.305s--
移动山东济南移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2006.024s0.195s0.588s2.802s--
移动黑龙江鸡西移动60.254.133.43日本/东京都/东京/阿卡迈2001.423s0.001s0.238s0.779s--
移动安徽黄山移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.029s0.208s0.602s1.191s--
移动江苏泰州移动23.51.117.84德国/北莱茵-威斯特法伦州/杜塞尔多夫/阿卡迈2003.116s0.004s0.661s1.481s--
移动河北唐山1移动--保留Failed10.003s0.000s0.000s0.000s----
移动湖南岳阳移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2004.497s0.554s1.644s1.116s--
移动四川乐山移动23.15.157.157新加坡/新加坡/新加坡/阿卡迈2006.907s0.053s0.284s6.222s--
移动山东烟台移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.529s0.546s0.650s1.268s--
移动浙江宁波移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.094s0.204s0.631s1.143s--
移动江苏盐城移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.664s0.195s0.600s1.291s--
移动江苏南通移动23.51.200.11美国/加利福尼亚州/埃尔塞贡多/akamai.com2003.998s0.278s0.787s0.943s--
移动辽宁鞍山移动--保留Failed10.002s0.000s0.000s0.000s----
移动河北唐山移动--保留Failed10.003s0.000s0.000s0.000s----
移动河南漯河移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2004.348s0.210s0.609s2.108s--
移动浙江金华移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2002.957s0.189s0.589s1.088s--
移动西藏拉萨移动--保留Failed10.005s0.000s0.000s0.000s----
移动青海海东移动--保留Failed10.008s0.000s0.000s0.000s----
移动新疆昌吉移动--保留Failed10.010s0.000s0.000s0.000s----
移动山西太原移动--保留Failed10.009s0.000s0.000s0.000s----
移动福建厦门移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2006.525s0.211s2.653s1.100s--
移动广西玉林移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2004.298s0.560s0.637s1.139s--
移动浙江温州移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2004.717s0.201s0.600s1.067s--
移动河南驻马店移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2009.229s0.136s1.551s3.409s--
移动广东湛江移动--保留Failed10.001s0.000s0.000s0.000s----
移动贵州黔南移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.692s0.211s0.674s1.555s--
移动河南信阳移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.535s0.214s0.630s1.046s--
移动云南昆明移动--保留Failed10.002s0.000s0.000s0.000s----
移动山西大同移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.153s0.217s0.668s0.986s--
移动四川广安移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.896s0.242s0.710s1.636s--
移动辽宁大连移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.272s0.222s0.666s1.118s--
移动山东聊城移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.540s0.206s0.604s1.334s--
移动山东菏泽移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.013s0.213s0.615s1.031s--
移动江苏苏州移动104.68.41.138印度尼西亚/雅加达/雅加达/阿卡迈Failed11.483s0.184s1.296s0.001s----
移动宁夏银川移动--保留Failed10.002s0.000s0.000s0.000s----
移动浙江杭州移动23.51.200.11美国/加利福尼亚州/埃尔塞贡多/akamai.com2003.563s0.253s0.827s1.178s--
移动湖南邵阳移动23.66.154.52中国/香港/香港/阿卡迈2000.991s0.001s0.099s0.636s--
移动宁夏中卫移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.667s0.222s0.639s1.553s--
移动广东广州移动--保留Failed10.002s0.000s0.000s0.000s----
移动广西柳州移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2006.442s0.208s1.631s3.309s--
移动江西宜春移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2006.092s0.219s1.662s2.584s--
移动辽宁盘锦移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2002.992s0.218s0.652s0.979s--
移动新疆伊犁移动--保留Failed10.003s0.000s0.000s0.000s----
移动甘肃威武移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.368s0.220s0.657s1.335s--
移动河南三门峡移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.532s0.212s0.635s1.461s--
移动重庆黔江移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.479s0.228s0.658s1.100s--
移动甘肃庆阳移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.349s0.226s0.662s1.302s--
移动陕西渭南移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2004.309s0.222s1.662s0.985s--
移动陕西西安移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.769s0.550s0.637s1.134s--
移动上海黄浦移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2009.042s0.108s1.621s3.282s--
移动广东河源移动--保留Failed10.002s0.000s0.000s0.000s----
移动广东东莞移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.084s0.193s0.591s1.298s--
移动广东广州1移动--保留Failed10.002s0.000s0.000s0.000s----
移动广东佛山移动--保留Failed10.011s0.000s0.000s0.000s----
移动河南鹤壁移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.196s0.205s0.616s1.181s--
移动四川成都移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2005.790s0.232s1.693s2.338s--
移动天津移动23.66.154.52中国/香港/香港/阿卡迈2001.152s0.005s0.165s0.776s--
移动 内蒙古包头移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.418s0.213s0.638s1.516s--
移动江西南昌移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2009.505s0.115s1.599s3.417s--
移动广西南宁移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2004.578s0.204s1.603s1.302s--
移动河南漯河1移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.468s0.210s0.610s1.186s--
移动安徽合肥移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.225s0.210s0.628s1.084s--
移动江西上饶移动104.68.97.254美国/加利福尼亚州/圣何塞/阿卡迈2003.664s0.223s0.670s1.236s--
移动湖北十堰移动--保留Failed10.002s0.000s0.000s0.000s----
移动湖北襄阳移动--保留Failed10.001s0.000s0.000s0.000s----

Website Speed Test Test Findings for store.playstation.com

Tested
Nov 20, 2026, 1:44 PM
Completed probes
82/82
Valid HTTP response probes
57 (70.4%)
Average total response time
4133 ms

This HTTP website speed test of store.playstation.com on 2026-11-20 returned valid HTTP responses from 57 of 81 observed nodes, a 70.4% response rate, with a median total response time of 3540 ms and P90 of 6475 ms. Two issues were detected

store.playstation.com HTTP speed test performance by network

Valid HTTP response rate counts probes with both a status code and total response time. P50 is the total time at or below which half of valid responses completed.

Valid HTTP response rate

Valid HTTP response rate (%)

70.4%Highest rate
Valid HTTP response rateValid HTTP response rate counts probes with both a status code and total response time. P50 is the total time at or below which half of valid responses completed.050100Mobile: 70.4%70.4%Mobile

P50 total response time

Total response time (ms)

3540 msLowest P50
P50 total response timeValid HTTP response rate counts probes with both a status code and total response time. P50 is the total time at or below which half of valid responses completed.01.9k3.8kMobile: 3540 ms3540 msMobile
Valid HTTP response rate counts probes with both a status code and total response time. P50 is the total time at or below which half of valid responses completed.

Key findings

  • 57 of 81 observed nodes obtained a valid HTTP response, giving a 70.4% response rate below the 95% reference threshold; 24 nodes did not obtain a valid response.
  • Median total response time was 3540 ms, above the 3000 ms warning threshold; P90 was 6475 ms, P95 8738 ms, and the average 4133 ms.
  • All 57 valid responses carried HTTP status code 200, with no other status codes observed; 7 distinct response IPs were observed.
  • Only the mobile carrier had usable samples (81 nodes, 70.4% response rate); telecom and unicom had none, and overseas had a single platform probe error excluded from the statistics, so no carrier comparison is supported.

Improvement recommendations

  • The HTTP response rate is 70.4%, below the 95% review threshold. Retest failed probes and use their status codes or network errors to inspect the CDN, reverse proxy, or origin only if failures persist.
  • P50 reached 3540 ms, above the 3000 ms review threshold. Repeat the same probes at a different time and investigate the relevant HTTP delivery path only if the elevated median persists.

These results describe this distributed test only and do not establish long-term availability, security, or a root cause.