DNS response history for ns1.jhc.one

ns1.jhc.one 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-25. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 526 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.jhc.one.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

526 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

44.232.222.174

Most recently resolved hosting IP on selected date

Successful Responses

29

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.jhc.one

Showing DNS history for 2026-08-25 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
29 2026-08-25 10:03 639232482235303141
390 ms 44.232.222.174
28 2026-08-25 09:45 639232471861770303
367 ms 44.232.222.174
27 2026-08-25 09:28 639232461630217327
215 ms 44.232.222.174
26 2026-08-25 09:11 639232451282965990
2269 ms 44.232.222.174
25 2026-08-25 08:53 639232440814614938
364 ms 44.232.222.174
24 2026-08-25 08:36 639232430410720425
343 ms 44.232.222.174
23 2026-08-25 08:19 639232420003096185
385 ms 44.232.222.174
22 2026-08-25 08:01 639232409467287444
2170 ms 44.232.222.174
21 2026-08-25 07:44 639232399077195997
345 ms 44.232.222.174
20 2026-08-25 07:26 639232388731528337
340 ms 44.232.222.174
19 2026-08-25 07:09 639232378288598612
349 ms 44.232.222.174
18 2026-08-25 06:15 639232346196373643
162 ms 44.232.222.174
17 2026-08-25 05:59 639232336112370741
370 ms 44.232.222.174
16 2026-08-25 05:42 639232326146508970
357 ms 44.232.222.174
15 2026-08-25 05:25 639232316189381720
371 ms 44.232.222.174
14 2026-08-25 05:09 639232306217998913
346 ms 44.232.222.174
13 2026-08-25 04:52 639232296255744174
170 ms 44.232.222.174
12 2026-08-25 04:35 639232286095760789
357 ms 44.232.222.174
11 2026-08-25 04:18 639232276086186273
171 ms 44.232.222.174
10 2026-08-25 04:02 639232265900986425
351 ms 44.232.222.174
9 2026-08-25 03:45 639232255723518075
360 ms 44.232.222.174
8 2026-08-25 03:28 639232245484452890
352 ms 44.232.222.174
7 2026-08-25 03:10 639232235157175331
356 ms 44.232.222.174
6 2026-08-25 02:17 639232203197189095
344 ms 44.232.222.174
5 2026-08-25 02:00 639232192844564298
332 ms 44.232.222.174
4 2026-08-25 01:43 639232182496008942
2262 ms 44.232.222.174
3 2026-08-25 01:26 639232172197053132
344 ms 44.232.222.174
2 2026-08-25 00:32 639232140250307418
351 ms 44.232.222.174
1 2026-08-25 00:15 639232129927860324
374 ms 44.232.222.174