DNS response history for ns2.theheightsfellowship.org

ns2.theheightsfellowship.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-26. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 426 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.theheightsfellowship.org.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

426 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.167.163.163

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 ns2.theheightsfellowship.org

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
27 2026-08-26 08:56 639233308387917838
75 ms 216.167.163.163
26 2026-08-26 08:39 639233297961740122
500 ms 216.167.163.163
25 2026-08-26 08:21 639233287487159094
277 ms 216.167.163.163
24 2026-08-26 08:04 639233276995531707
301 ms 216.167.163.163
23 2026-08-26 07:46 639233266521568229
405 ms 216.167.163.163
22 2026-08-26 07:29 639233256081047431
274 ms 216.167.163.163
21 2026-08-26 06:35 639233223620132921
161 ms 216.167.163.163
20 2026-08-26 06:18 639233213287814244
398 ms 216.167.163.163
19 2026-08-26 06:00 639233202925983161
7 ms 216.167.163.163
18 2026-08-26 05:43 639233192644780696
274 ms 216.167.163.163
17 2026-08-26 05:26 639233182401183833
167 ms 216.167.163.163
16 2026-08-26 05:09 639233172074181051
381 ms 216.167.163.163
15 2026-08-26 04:52 639233161808421455
146 ms 216.167.163.163
14 2026-08-26 04:34 639233151357344052
298 ms 216.167.163.163
13 2026-08-26 04:17 639233141034116946
623 ms 216.167.163.163
12 2026-08-26 04:00 639233130828334142
302 ms 216.167.163.163
11 2026-08-26 03:43 639233120373450007
262 ms 216.167.163.163
10 2026-08-26 03:25 639233110066216193
381 ms 216.167.163.163
9 2026-08-26 02:32 639233078065410564
176 ms 216.167.163.163
8 2026-08-26 02:15 639233067787457832
2129 ms 216.167.163.163
7 2026-08-26 01:58 639233057501801162
278 ms 216.167.163.163
6 2026-08-26 01:41 639233047089431703
441 ms 216.167.163.163
5 2026-08-26 01:23 639233036754790688
7 ms 216.167.163.163
4 2026-08-26 01:06 639233026412602472
373 ms 216.167.163.163
3 2026-08-26 00:49 639233016064066127
704 ms 216.167.163.163
2 2026-08-26 00:32 639233005922655772
157 ms 216.167.163.163
1 2026-08-26 00:15 639232995672256907
2007 ms 216.167.163.163