DNS response history for ns.johnrunkle.net

ns.johnrunkle.net 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 36 DNS check records, 36 successful responses, 0 failed responses, and 381 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 ns.johnrunkle.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

381 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.58.85.254

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns.johnrunkle.net

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
36 2026-08-26 11:56 639233414056832719
118 ms 50.58.85.254
35 2026-08-26 11:39 639233403515141099
464 ms 50.58.85.254
34 2026-08-26 10:44 639233370841350248
465 ms 50.58.85.254
33 2026-08-26 10:27 639233360361507238
452 ms 50.58.85.254
32 2026-08-26 10:09 639233350067824371
15 ms 50.58.85.254
31 2026-08-26 09:52 639233339545274518
567 ms 50.58.85.254
30 2026-08-26 09:35 639233329214918079
500 ms 50.58.85.254
29 2026-08-26 09:17 639233318749762337
460 ms 50.58.85.254
28 2026-08-26 09:00 639233308387917838
464 ms 50.58.85.254
27 2026-08-26 08:43 639233297961740122
10 ms 50.58.85.254
26 2026-08-26 08:25 639233287487159094
464 ms 50.58.85.254
25 2026-08-26 08:08 639233276995531707
458 ms 50.58.85.254
24 2026-08-26 07:50 639233266521568229
562 ms 50.58.85.254
23 2026-08-26 07:33 639233256081047431
127 ms 50.58.85.254
22 2026-08-26 06:39 639233223620132921
452 ms 50.58.85.254
21 2026-08-26 06:22 639233213287814244
470 ms 50.58.85.254
20 2026-08-26 06:04 639233202925983161
458 ms 50.58.85.254
19 2026-08-26 05:47 639233192644780696
454 ms 50.58.85.254
18 2026-08-26 05:30 639233182401183833
120 ms 50.58.85.254
17 2026-08-26 05:13 639233172074181051
457 ms 50.58.85.254
16 2026-08-26 04:56 639233161808421455
457 ms 50.58.85.254
15 2026-08-26 04:39 639233151357344052
459 ms 50.58.85.254
14 2026-08-26 04:21 639233141034116946
4 ms 50.58.85.254
13 2026-08-26 04:04 639233130828334142
557 ms 50.58.85.254
12 2026-08-26 03:47 639233120373450007
3 ms 50.58.85.254
11 2026-08-26 03:29 639233110066216193
454 ms 50.58.85.254
10 2026-08-26 02:36 639233078065410564
455 ms 50.58.85.254
9 2026-08-26 02:19 639233067787457832
457 ms 50.58.85.254
8 2026-08-26 02:02 639233057501801162
112 ms 50.58.85.254
7 2026-08-26 01:45 639233047089431703
466 ms 50.58.85.254
6 2026-08-26 01:27 639233036754790688
461 ms 50.58.85.254
5 2026-08-26 01:10 639233026412602472
453 ms 50.58.85.254
4 2026-08-26 00:53 639233016064066127
457 ms 50.58.85.254
3 2026-08-26 00:36 639233005922655772
469 ms 50.58.85.254
2 2026-08-26 00:19 639232995672256907
471 ms 50.58.85.254
1 2026-08-26 00:02 639232985300872416
456 ms 50.58.85.254