DNS response history for ns2.haxcdn.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

608 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

114.236.93.101

Most recently resolved hosting IP on selected date

Successful Responses

34

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.haxcdn.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
34 2026-08-26 10:46 639233370841350248
809 ms 114.236.93.101
33 2026-08-26 10:29 639233360361507238
1391 ms 114.236.93.101
32 2026-08-26 10:11 639233350067824371
1319 ms 114.236.93.101
31 2026-08-26 09:54 639233339545274518
741 ms 114.236.93.101
30 2026-08-26 09:36 639233329214918079
202 ms 114.236.93.101
29 2026-08-26 09:19 639233318749762337
747 ms 114.236.93.101
28 2026-08-26 09:02 639233308387917838
215 ms 114.236.93.101
27 2026-08-26 08:44 639233297961740122
458 ms 114.236.93.101
26 2026-08-26 08:27 639233287487159094
1016 ms 114.236.93.101
25 2026-08-26 08:10 639233276995531707
982 ms 114.236.93.101
24 2026-08-26 07:52 639233266521568229
441 ms 114.236.93.101
23 2026-08-26 07:35 639233256081047431
501 ms 114.236.93.101
22 2026-08-26 06:41 639233223620132921
463 ms 114.236.93.101
21 2026-08-26 06:23 639233213287814244
3 ms 114.236.93.101
20 2026-08-26 06:06 639233202925983161
2007 ms 114.236.93.101
19 2026-08-26 05:49 639233192644780696
182 ms 114.236.93.101
18 2026-08-26 05:32 639233182401183833
961 ms 114.236.93.101
17 2026-08-26 05:15 639233172074181051
392 ms 114.236.93.101
16 2026-08-26 04:57 639233161808421455
517 ms 114.236.93.101
15 2026-08-26 04:40 639233151357344052
2280 ms 114.236.93.101
14 2026-08-26 04:23 639233141034116946
4 ms 114.236.93.101
13 2026-08-26 04:06 639233130828334142
3 ms 114.236.93.101
12 2026-08-26 03:48 639233120373450007
408 ms 114.236.93.101
11 2026-08-26 03:31 639233110066216193
446 ms 114.236.93.101
10 2026-08-26 02:38 639233078065410564
920 ms 114.236.93.101
9 2026-08-26 02:21 639233067787457832
3 ms 114.236.93.101
8 2026-08-26 02:04 639233057501801162
998 ms 114.236.93.101
7 2026-08-26 01:46 639233047089431703
3 ms 114.236.93.101
6 2026-08-26 01:29 639233036754790688
9 ms 114.236.93.101
5 2026-08-26 01:12 639233026412602472
461 ms 114.236.93.101
4 2026-08-26 00:55 639233016064066127
931 ms 114.236.93.101
3 2026-08-26 00:37 639233005922655772
432 ms 114.236.93.101
2 2026-08-26 00:20 639232995672256907
206 ms 114.236.93.101
1 2026-08-26 00:03 639232985300872416
214 ms 114.236.93.101