DNS response history for ns2.haitong.com

ns2.haitong.com is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-26. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 279 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns2.haitong.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

279 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

140.206.175.4

Most recently resolved hosting IP on selected date

Successful Responses

26

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.haitong.com

Showing DNS history for 2026-08-26 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
26 2026-08-26 08:27 639233287487159094
398 ms 140.206.175.4
25 2026-08-26 08:09 639233276995531707
209 ms 140.206.175.4
24 2026-08-26 07:52 639233266521568229
405 ms 140.206.175.4
23 2026-08-26 07:34 639233256081047431
200 ms 140.206.175.4
22 2026-08-26 06:40 639233223620132921
206 ms 140.206.175.4
21 2026-08-26 06:23 639233213287814244
197 ms 140.206.175.4
20 2026-08-26 06:06 639233202925983161
208 ms 140.206.175.4
19 2026-08-26 05:48 639233192644780696
194 ms 140.206.175.4
18 2026-08-26 05:31 639233182401183833
204 ms 140.206.175.4
17 2026-08-26 05:14 639233172074181051
417 ms 140.206.175.4
16 2026-08-26 04:57 639233161808421455
201 ms 140.206.175.4
15 2026-08-26 04:40 639233151357344052
273 ms 140.206.175.4
14 2026-08-26 04:22 639233141034116946
390 ms 140.206.175.4
13 2026-08-26 04:05 639233130828334142
198 ms 140.206.175.4
12 2026-08-26 03:48 639233120373450007
401 ms 140.206.175.4
11 2026-08-26 03:31 639233110066216193
204 ms 140.206.175.4
10 2026-08-26 02:37 639233078065410564
402 ms 140.206.175.4
9 2026-08-26 02:20 639233067787457832
298 ms 140.206.175.4
8 2026-08-26 02:03 639233057501801162
205 ms 140.206.175.4
7 2026-08-26 01:46 639233047089431703
197 ms 140.206.175.4
6 2026-08-26 01:29 639233036754790688
402 ms 140.206.175.4
5 2026-08-26 01:11 639233026412602472
421 ms 140.206.175.4
4 2026-08-26 00:54 639233016064066127
206 ms 140.206.175.4
3 2026-08-26 00:37 639233005922655772
208 ms 140.206.175.4
2 2026-08-26 00:20 639232995672256907
205 ms 140.206.175.4
1 2026-08-26 00:03 639232985300872416
406 ms 140.206.175.4