DNS response history for ns1.healthsyncdaily.info

ns1.healthsyncdaily.info 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-09-01. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 323 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 ns1.healthsyncdaily.info.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

323 ms

Calculated from available response records

Latest Check on Selected Date

2026-09-01 12:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

167.71.245.7

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns1.healthsyncdaily.info

Showing DNS history for 2026-09-01 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
37 2026-09-01 12:47 639238628486902752
252 ms 167.71.245.7
36 2026-09-01 12:30 639238617906743100
107 ms 167.71.245.7
35 2026-09-01 12:12 639238607506044626
105 ms 167.71.245.7
34 2026-09-01 11:55 639238597040761406
107 ms 167.71.245.7
33 2026-09-01 11:37 639238586261546969
241 ms 167.71.245.7
32 2026-09-01 11:19 639238575587642333
423 ms 167.71.245.7
31 2026-09-01 10:25 639238543127398267
102 ms 167.71.245.7
30 2026-09-01 10:08 639238532668234016
427 ms 167.71.245.7
29 2026-09-01 09:50 639238522029321761
231 ms 167.71.245.7
28 2026-09-01 09:32 639238511519050351
105 ms 167.71.245.7
27 2026-09-01 09:15 639238500942239673
104 ms 167.71.245.7
26 2026-09-01 08:57 639238490412377398
3 ms 167.71.245.7
25 2026-09-01 08:40 639238479833203021
106 ms 167.71.245.7
24 2026-09-01 08:22 639238469140507479
217 ms 167.71.245.7
23 2026-09-01 08:04 639238458443560361
339 ms 167.71.245.7
22 2026-09-01 07:46 639238447694851502
577 ms 167.71.245.7
21 2026-09-01 07:28 639238436624109087
213 ms 167.71.245.7
20 2026-09-01 07:10 639238425565611335
602 ms 167.71.245.7
19 2026-09-01 06:14 639238392250222581
431 ms 167.71.245.7
18 2026-09-01 05:56 639238381322537831
566 ms 167.71.245.7
17 2026-09-01 05:38 639238370248186084
423 ms 167.71.245.7
16 2026-09-01 05:19 639238359264687845
217 ms 167.71.245.7
15 2026-09-01 05:01 639238348534621818
424 ms 167.71.245.7
14 2026-09-01 04:43 639238337725739433
454 ms 167.71.245.7
13 2026-09-01 04:25 639238326844749368
421 ms 167.71.245.7
12 2026-09-01 04:07 639238315792024737
430 ms 167.71.245.7
11 2026-09-01 03:49 639238304931064768
375 ms 167.71.245.7
10 2026-09-01 03:30 639238294131483803
377 ms 167.71.245.7
9 2026-09-01 03:12 639238283314985519
375 ms 167.71.245.7
8 2026-09-01 02:54 639238272374093187
370 ms 167.71.245.7
7 2026-09-01 02:00 639238240032549922
379 ms 167.71.245.7
6 2026-09-01 01:42 639238229204177368
372 ms 167.71.245.7
5 2026-09-01 01:24 639238218326150282
379 ms 167.71.245.7
4 2026-09-01 01:06 639238207574700853
374 ms 167.71.245.7
3 2026-09-01 00:48 639238196660283915
372 ms 167.71.245.7
2 2026-09-01 00:30 639238185782358546
374 ms 167.71.245.7
1 2026-09-01 00:12 639238175054391781
580 ms 167.71.245.7