DNS response history for ns3.jrchurch.org

ns3.jrchurch.org 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-24. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 626 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 ns3.jrchurch.org.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

626 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.126.143.225

Most recently resolved hosting IP on selected date

Successful Responses

27

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 ns3.jrchurch.org

Showing DNS history for 2026-08-24 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
27 2026-08-24 11:36 639231673513573868
791 ms 116.126.143.225
26 2026-08-24 10:43 639231641791249939
689 ms 116.126.143.225
25 2026-08-24 10:27 639231631866211033
847 ms 116.126.143.225
24 2026-08-24 10:10 639231621644955316
826 ms 116.126.143.225
23 2026-08-24 09:53 639231611478799259
1167 ms 116.126.143.225
22 2026-08-24 09:00 639231579923718211
567 ms 116.126.143.225
21 2026-08-24 08:44 639231569810702936
839 ms 116.126.143.225
20 2026-08-24 08:27 639231559762411619
593 ms 116.126.143.225
19 2026-08-24 08:10 639231549663595407
1165 ms 116.126.143.225
18 2026-08-24 07:17 639231518076817246
3 ms 116.126.143.225
17 2026-08-24 07:01 639231508078650885
953 ms 116.126.143.225
16 2026-08-24 06:44 639231498210697093
343 ms 116.126.143.225
15 2026-08-24 06:27 639231488109699360
864 ms 116.126.143.225
14 2026-08-24 05:35 639231456772510692
328 ms 116.126.143.225
13 2026-08-24 05:19 639231447084631185
10 ms 116.126.143.225
12 2026-08-24 05:02 639231437208519473
884 ms 116.126.143.225
11 2026-08-24 04:46 639231427209627490
715 ms 116.126.143.225
10 2026-08-24 03:53 639231395791246644
292 ms 116.126.143.225
9 2026-08-24 03:37 639231386075551458
3 ms 116.126.143.225
8 2026-08-24 03:21 639231376208713791
288 ms 116.126.143.225
7 2026-08-24 03:04 639231366170589276
1217 ms 116.126.143.225
6 2026-08-24 02:12 639231334732159368
590 ms 116.126.143.225
5 2026-08-24 01:55 639231325035670078
307 ms 116.126.143.225
4 2026-08-24 01:39 639231315132253837
1191 ms 116.126.143.225
3 2026-08-24 01:22 639231305014280808
287 ms 116.126.143.225
2 2026-08-24 00:30 639231273779380675
1144 ms 116.126.143.225
1 2026-08-24 00:14 639231264180839154
3 ms 116.126.143.225