104.233.219.12 Speed Test

Carrier
DNS

Nationwide Speed Map

Nationwide Speed Map
  • >10s
  • 3s-10s
  • 1s-3s
  • 0.5s-1s
  • <=0.5s
100%
RegionFastestSlowestAverage
All Nodes上海数据中心 13.6396s宿迁电信 26.8082s20.741s
China Telecom四川广安电信 16.047s宿迁电信 26.8082s21.555s
China Unicom上海数据中心 13.6396s甘肃联通 22.9586s18.299s
China Mobile------
East China上海数据中心 13.6396s宿迁电信 26.8082s20.224s
South China------
Central China湖北十堰电信 19.8561s湖北十堰电信 19.8561s19.856s
North China北京电信 18.7868s河北电信 24.4968s21.642s
Southwest四川广安电信 16.047s四川广安电信 16.047s16.047s
Northwest甘肃联通 22.9586s电信青海 23.3334s23.146s
Northeast------
HK/MO/TW------

DNS Resolution Stats

1

Showing: 11/11

NodeResponse IPIP LocationStatusTotalResolveConnectDownloadRedirectHead
电信湖北十堰电信104.233.219.12日本/东京都/东京/PEG TECH INC40319.8561s0.0001s0.1228s19.7314s--
电信四川广安电信104.233.219.12日本/东京都/东京/PEG TECH INC40316.047s0.0017s0.1527s15.8895s--
电信河北电信104.233.219.12日本/东京都/东京/PEG TECH INC40324.4968s0.0001s0.1298s24.3663s--
电信北京电信104.233.219.12日本/东京都/东京/PEG TECH INC40318.7868s0.0001s0.1061s18.6801s--
联通甘肃联通104.233.219.12日本/东京都/东京/PEG TECH INC40322.9586s0.0001s0.1354s22.8219s--
联通上海数据中心104.233.219.12日本/东京都/东京/PEG TECH INC40313.6396s0.0001s0.067s13.5721s--
海外俄罗斯莫斯科104.233.219.12日本/东京都/东京/PEG TECH INC40329.2927s0.0001s7.1906s22.1012s--
海外柬埔寨金边104.233.219.12日本/东京都/东京/PEG TECH INC40326.3842s0.0001s0.2231s26.1602s--
海外迪拜104.233.219.12日本/东京都/东京/PEG TECH INC40329.4758s0.0001s0.7567s28.718s--
电信电信青海104.233.219.12日本/东京都/东京/PEG TECH INC40323.3334s0.0003s0.1551s23.1773s--
电信宿迁电信104.233.219.12日本/东京都/东京/PEG TECH INC40326.8082s0.0002s0.2034s26.6015s--

Website Speed Test Test Findings for 104.233.219.12

Tested
Oct 19, 2026, 12:00 AM
Completed probes
305/305
Valid HTTP response probes
11 (100%)
Average total response time
22825 ms

This HTTP website speed test covered 305 nodes, all of which responded, giving a 100% response rate. However, no node obtained a valid HTTP 2xx response; every status code was 403. Median total response time was 2627 ms and the 95th percent

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

18299 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.014.8k29.5kTelecom: 21595 ms21595 msTelecomUnicom: 18299 ms18299 msUnicomOverseas: 29293 ms29293 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 305 nodes returned HTTP 403 and http2xxCount was 0, so this test did not obtain a valid HTTP response.
  • The response rate was 100%, unavailableNodeCount was 0 and nodeErrorCount was 0, indicating that every node completed its probe and received a reply.
  • Median total response time was 2627 ms, with a 90th percentile of 5014 ms, a 95th percentile of 7542 ms and an overall average of 3790 ms.
  • Overseas nodes averaged 7747 ms, above telecom at 3889 ms, unicom at 3457 ms and mobile at 2309 ms; only one response IP was observed.

Improvement recommendations

  • P50 reached 23333 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.
  • P95 reached 29384 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.