663322.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.0949s宿迁电信 3.1983s0.857s
China Telecom河北电信 0.0949s宿迁电信 3.1983s0.982s
China Unicom上海数据中心 0.1089s上海数据中心 0.1089s0.109s
China Mobile------
East China上海数据中心 0.1089s宿迁电信 3.1983s1.654s
South China------
Central China湖北十堰电信 0.3s湖北十堰电信 0.3s0.300s
North China河北电信 0.0949s北京电信 0.2699s0.182s
Southwest四川广安电信 0.1234s四川广安电信 0.1234s0.123s
Northwest电信青海 1.9026s电信青海 1.9026s1.903s
Northeast------
HK/MO/TW------

DNS Resolution Stats

4

Showing: 10/10

NodeResponse IPIP LocationStatusTotalResolveConnectDownloadRedirectHead
电信湖北十堰电信125.94.244.61中国/广东/佛山市/电信2000.3s0.2393s0.0589s0.0008s--
电信四川广安电信125.94.244.61中国/广东/佛山市/电信2000.1234s0.0592s0.0625s0.0005s--
电信河北电信103.71.70.43中国/江苏/常州市/电信2000.0949s0.0265s0.0559s0.0122s--
电信北京电信103.71.70.43中国/江苏/常州市/电信2000.2699s0.1839s0.055s0.0307s--
联通上海数据中心103.71.70.43中国/江苏/常州市/电信2000.1089s0.0727s0.0247s0.0114s--
海外俄罗斯莫斯科107.148.2.126日本/东京都/东京/PEG TECH INC2000.9923s0.4757s0.5158s0.0005s--
海外柬埔寨金边107.148.2.126日本/东京都/东京/PEG TECH INC2000.4237s0.2037s0.2192s0.0005s--
海外迪拜107.148.2.126日本/东京都/东京/PEG TECH INC2006.4737s6.1568s0.3161s0.0005s--
电信电信青海103.71.70.43中国/江苏/常州市/电信2001.9026s1.6441s0.1581s0.1002s--
电信宿迁电信180.109.0.221中国/江苏/南京市/电信5033.1983s0.0109s3.1855s0.0005s--

Website Speed Test Test Findings for 663322.com

Tested
Oct 18, 2026, 12:40 PM
Completed probes
305/305
Valid HTTP response probes
10 (100%)
Average total response time
1389 ms

This HTTP website speed test on 2026-10-13 covered 295 nodes with a 98.3% response rate; median total response time was 263 ms and P90 was 978 ms. Overseas nodes were notably slower, but no clear anomaly requiring action was found.

663322.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 (%)

100%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.050100Telecom: 100%100%TelecomUnicom: 100%100%UnicomOverseas: 100%100%Overseas

P50 total response time

Total response time (ms)

109 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.05001kTelecom: 285 ms285 msTelecomUnicom: 109 ms109 msUnicomOverseas: 992 ms992 msOverseas
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

  • Of 295 nodes, 290 returned a valid HTTP response, a 98.3% response rate, mostly status code 200, plus 2 responses with 302 and 1 with 403.
  • Median total response time was 263 ms, P90 978 ms and P95 1754 ms, so most nodes fell in a relatively fast range.
  • Overseas nodes showed a median of 914 ms and P90 of 2435 ms, clearly above telecom, unicom and mobile.
  • Observed response IP diversity was 16 addresses, and nodeErrorCount was 0, excluded from unavailable nodes.

Improvement recommendations

  • 1 probes returned HTTP 5xx responses. Retest those probes and, if the responses persist, inspect the CDN or origin error logs for the test time before validating again.

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