DNS response history for ns2.hitpub.com

ns2.hitpub.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 474 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.hitpub.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

474 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.197.165.75

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.hitpub.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:26 639233287487159094
535 ms 61.197.165.75
25 2026-08-26 08:08 639233276995531707
535 ms 61.197.165.75
24 2026-08-26 07:51 639233266521568229
534 ms 61.197.165.75
23 2026-08-26 07:33 639233256081047431
533 ms 61.197.165.75
22 2026-08-26 06:39 639233223620132921
533 ms 61.197.165.75
21 2026-08-26 06:22 639233213287814244
533 ms 61.197.165.75
20 2026-08-26 06:05 639233202925983161
533 ms 61.197.165.75
19 2026-08-26 05:47 639233192644780696
534 ms 61.197.165.75
18 2026-08-26 05:30 639233182401183833
543 ms 61.197.165.75
17 2026-08-26 05:13 639233172074181051
531 ms 61.197.165.75
16 2026-08-26 04:56 639233161808421455
543 ms 61.197.165.75
15 2026-08-26 04:39 639233151357344052
534 ms 61.197.165.75
14 2026-08-26 04:22 639233141034116946
272 ms 61.197.165.75
13 2026-08-26 04:04 639233130828334142
531 ms 61.197.165.75
12 2026-08-26 03:47 639233120373450007
529 ms 61.197.165.75
11 2026-08-26 03:30 639233110066216193
530 ms 61.197.165.75
10 2026-08-26 02:37 639233078065410564
4 ms 61.197.165.75
9 2026-08-26 02:19 639233067787457832
531 ms 61.197.165.75
8 2026-08-26 02:02 639233057501801162
531 ms 61.197.165.75
7 2026-08-26 01:45 639233047089431703
292 ms 61.197.165.75
6 2026-08-26 01:28 639233036754790688
548 ms 61.197.165.75
5 2026-08-26 01:11 639233026412602472
530 ms 61.197.165.75
4 2026-08-26 00:53 639233016064066127
553 ms 61.197.165.75
3 2026-08-26 00:36 639233005922655772
4 ms 61.197.165.75
2 2026-08-26 00:19 639232995672256907
525 ms 61.197.165.75
1 2026-08-26 00:02 639232985300872416
529 ms 61.197.165.75