104.233.147.13 Speed Test

Carrier
DNS

Nationwide Speed Map

Nationwide Speed Map
  • >10s
  • 3s-10s
  • 1s-3s
  • 0.5s-1s
  • <=0.5s
100%
RegionFastestSlowestAverage
All Nodes上海数据中心 1.5424s湖北十堰电信 26.9804s5.439s
China Telecom河北电信 1.6052s湖北十堰电信 26.9804s6.369s
China Unicom上海数据中心 1.5424s甘肃联通 2.8243s2.183s
China Mobile------
East China上海数据中心 1.5424s宿迁电信 5.4944s3.518s
South China------
Central China湖北十堰电信 26.9804s湖北十堰电信 26.9804s26.980s
North China河北电信 1.6052s北京电信 2.3871s1.996s
Southwest贵州贵阳电信 1.7681s四川广安电信 4.5758s3.172s
Northwest电信青海 1.7709s甘肃联通 2.8243s2.298s
Northeast------
HK/MO/TW------

DNS Resolution Stats

1

Showing: 11/11

NodeResponse IPIP LocationStatusTotalResolveConnectDownloadRedirectHead
电信贵州贵阳电信104.233.147.13美国/加利福尼亚州/旧金山/PEG TECH INC4031.7681s0.0001s0.3611s1.4061s--
电信湖北十堰电信104.233.147.13美国/加利福尼亚州/旧金山/PEG TECH INC40326.9804s0.0003s0.3635s26.6144s--
电信四川广安电信104.233.147.13美国/加利福尼亚州/旧金山/PEG TECH INC4034.5758s0.0001s0.3544s4.2191s--
电信河北电信104.233.147.13美国/加利福尼亚州/旧金山/PEG TECH INC4031.6052s0.0001s0.3241s1.2806s--
电信北京电信104.233.147.13美国/加利福尼亚州/旧金山/PEG TECH INC4032.3871s0.0001s0.3151s2.0715s--
联通甘肃联通104.233.147.13美国/加利福尼亚州/旧金山/PEG TECH INC4032.8243s0.0001s0.3583s2.4651s--
联通上海数据中心104.233.147.13美国/加利福尼亚州/旧金山/PEG TECH INC4031.5424s0s0.3112s1.2308s--
海外俄罗斯莫斯科104.233.147.13美国/加利福尼亚州/旧金山/PEG TECH INC4031.8665s0.0001s0.3674s1.4985s--
海外柬埔寨金边104.233.147.13美国/加利福尼亚州/旧金山/PEG TECH INC4032.1002s0.0001s0.4186s1.6807s--
电信电信青海104.233.147.13美国/加利福尼亚州/旧金山/PEG TECH INC4031.7709s0.0001s0.3581s1.4124s--
电信宿迁电信104.233.147.13美国/加利福尼亚州/旧金山/PEG TECH INC4035.4944s0.0006s0.3972s5.0946s--

Website Speed Test Test Findings for 104.233.147.13

Tested
Oct 25, 2026, 11:24 PM
Completed probes
308/308
Valid HTTP response probes
11 (100%)
Average total response time
4810 ms

This HTTP website speed test ran on 2026-10-25 across 308 nodes with a 98.1% response rate; median total response time was 339 ms and P95 was 574 ms. Every responding node returned HTTP 403, so no 2xx valid HTTP response was obtained.

104.233.147.13 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)

1983 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.3k2.5kTelecom: 2387 ms2387 msTelecomUnicom: 2183 ms2183 msUnicomOverseas: 1983 ms1983 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

  • All 302 responding nodes returned HTTP 403 and http2xxCount was 0, so the test did not obtain the valid HTTP response it defines.
  • Median total response time was 339 ms, P90 412 ms and P95 574 ms; carrier medians ranged from 328 to 348 ms.
  • Response rates were 97.6% for telecom, 96.2% for mobile, and 100% for unicom and overseas, with 6 nodes not responding; platform probe failures were 0.
  • Observed response IP diversity was 1 address; this observation alone is not treated as an anomaly.

Improvement recommendations

  • P95 reached 16237 ms, above the 10000 ms review threshold. Retest the slow probes and compare their routes or service stages before changing production configuration.

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