DNS response history for ns2.haiyu.com

ns2.haiyu.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 31 DNS check records, 31 successful responses, 0 failed responses, and 1822 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.haiyu.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

1822 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

173.242.120.123

Most recently resolved hosting IP on selected date

Successful Responses

31

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.haiyu.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
31 2026-08-26 09:55 639233339545274518
2194 ms 173.242.120.123
30 2026-08-26 09:38 639233329214918079
2009 ms 173.242.120.123
29 2026-08-26 09:20 639233318749762337
2262 ms 173.242.120.123
28 2026-08-26 09:03 639233308387917838
2202 ms 173.242.120.123
27 2026-08-26 08:46 639233297961740122
2223 ms 173.242.120.123
26 2026-08-26 08:28 639233287487159094
2299 ms 173.242.120.123
25 2026-08-26 08:11 639233276995531707
2246 ms 173.242.120.123
24 2026-08-26 07:53 639233266521568229
2212 ms 173.242.120.123
23 2026-08-26 07:36 639233256081047431
2376 ms 173.242.120.123
22 2026-08-26 06:42 639233223620132921
3515 ms 173.242.120.123
21 2026-08-26 06:24 639233213287814244
2299 ms 173.242.120.123
20 2026-08-26 06:07 639233202925983161
2007 ms 173.242.120.123
19 2026-08-26 05:50 639233192644780696
2321 ms 173.242.120.123
18 2026-08-26 05:33 639233182401183833
2032 ms 173.242.120.123
17 2026-08-26 05:16 639233172074181051
2273 ms 173.242.120.123
16 2026-08-26 04:59 639233161808421455
2231 ms 173.242.120.123
15 2026-08-26 04:41 639233151357344052
2009 ms 173.242.120.123
14 2026-08-26 04:24 639233141034116946
2172 ms 173.242.120.123
13 2026-08-26 04:07 639233130828334142
3 ms 173.242.120.123
12 2026-08-26 03:50 639233120373450007
2162 ms 173.242.120.123
11 2026-08-26 03:32 639233110066216193
2011 ms 173.242.120.123
10 2026-08-26 02:39 639233078065410564
2246 ms 173.242.120.123
9 2026-08-26 02:22 639233067787457832
2232 ms 173.242.120.123
8 2026-08-26 02:05 639233057501801162
4 ms 173.242.120.123
7 2026-08-26 01:48 639233047089431703
2 ms 173.242.120.123
6 2026-08-26 01:30 639233036754790688
3 ms 173.242.120.123
5 2026-08-26 01:13 639233026412602472
2286 ms 173.242.120.123
4 2026-08-26 00:56 639233016064066127
2453 ms 173.242.120.123
3 2026-08-26 00:39 639233005922655772
2 ms 173.242.120.123
2 2026-08-26 00:22 639232995672256907
2 ms 173.242.120.123
1 2026-08-26 00:05 639232985300872416
2197 ms 173.242.120.123