DNS response history for ns2.havingchurchesministries.com

ns2.havingchurchesministries.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 29 DNS check records, 29 successful responses, 0 failed responses, and 131 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.havingchurchesministries.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

131 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.6.160.170

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 ns2.havingchurchesministries.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
29 2026-08-26 09:29 639233329214918079
21 ms 50.6.160.170
28 2026-08-26 09:12 639233318749762337
2128 ms 50.6.160.170
27 2026-08-26 08:55 639233308387917838
129 ms 50.6.160.170
26 2026-08-26 08:37 639233297961740122
115 ms 50.6.160.170
25 2026-08-26 08:20 639233287487159094
11 ms 50.6.160.170
24 2026-08-26 08:03 639233276995531707
39 ms 50.6.160.170
23 2026-08-26 07:45 639233266521568229
3 ms 50.6.160.170
22 2026-08-26 07:28 639233256081047431
110 ms 50.6.160.170
21 2026-08-26 06:34 639233223620132921
125 ms 50.6.160.170
20 2026-08-26 06:16 639233213287814244
3 ms 50.6.160.170
19 2026-08-26 05:59 639233202925983161
5 ms 50.6.160.170
18 2026-08-26 05:42 639233192644780696
4 ms 50.6.160.170
17 2026-08-26 05:25 639233182401183833
20 ms 50.6.160.170
16 2026-08-26 05:08 639233172074181051
115 ms 50.6.160.170
15 2026-08-26 04:51 639233161808421455
19 ms 50.6.160.170
14 2026-08-26 04:33 639233151357344052
120 ms 50.6.160.170
13 2026-08-26 04:16 639233141034116946
153 ms 50.6.160.170
12 2026-08-26 03:59 639233130828334142
7 ms 50.6.160.170
11 2026-08-26 03:42 639233120373450007
3 ms 50.6.160.170
10 2026-08-26 03:24 639233110066216193
106 ms 50.6.160.170
9 2026-08-26 02:31 639233078065410564
4 ms 50.6.160.170
8 2026-08-26 02:14 639233067787457832
4 ms 50.6.160.170
7 2026-08-26 01:57 639233057501801162
3 ms 50.6.160.170
6 2026-08-26 01:39 639233047089431703
115 ms 50.6.160.170
5 2026-08-26 01:22 639233036754790688
117 ms 50.6.160.170
4 2026-08-26 01:05 639233026412602472
3 ms 50.6.160.170
3 2026-08-26 00:48 639233016064066127
25 ms 50.6.160.170
2 2026-08-26 00:31 639233005922655772
102 ms 50.6.160.170
1 2026-08-26 00:14 639232995672256907
189 ms 50.6.160.170