DNS response history for ns2.harperangel.com

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

26

Historical checks stored for this nameserver on selected date

Average Latency

780 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.3.117.102

Most recently resolved hosting IP on selected date

Successful Responses

26

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.harperangel.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
26 2026-08-26 08:26 639233287487159094
810 ms 50.3.117.102
25 2026-08-26 08:09 639233276995531707
810 ms 50.3.117.102
24 2026-08-26 07:51 639233266521568229
824 ms 50.3.117.102
23 2026-08-26 07:34 639233256081047431
818 ms 50.3.117.102
22 2026-08-26 06:40 639233223620132921
808 ms 50.3.117.102
21 2026-08-26 06:22 639233213287814244
816 ms 50.3.117.102
20 2026-08-26 06:05 639233202925983161
804 ms 50.3.117.102
19 2026-08-26 05:48 639233192644780696
801 ms 50.3.117.102
18 2026-08-26 05:31 639233182401183833
803 ms 50.3.117.102
17 2026-08-26 05:14 639233172074181051
810 ms 50.3.117.102
16 2026-08-26 04:56 639233161808421455
824 ms 50.3.117.102
15 2026-08-26 04:39 639233151357344052
813 ms 50.3.117.102
14 2026-08-26 04:22 639233141034116946
802 ms 50.3.117.102
13 2026-08-26 04:05 639233130828334142
800 ms 50.3.117.102
12 2026-08-26 03:48 639233120373450007
803 ms 50.3.117.102
11 2026-08-26 03:30 639233110066216193
808 ms 50.3.117.102
10 2026-08-26 02:37 639233078065410564
810 ms 50.3.117.102
9 2026-08-26 02:20 639233067787457832
824 ms 50.3.117.102
8 2026-08-26 02:03 639233057501801162
804 ms 50.3.117.102
7 2026-08-26 01:46 639233047089431703
806 ms 50.3.117.102
6 2026-08-26 01:28 639233036754790688
812 ms 50.3.117.102
5 2026-08-26 01:11 639233026412602472
808 ms 50.3.117.102
4 2026-08-26 00:54 639233016064066127
3 ms 50.3.117.102
3 2026-08-26 00:37 639233005922655772
808 ms 50.3.117.102
2 2026-08-26 00:20 639232995672256907
826 ms 50.3.117.102
1 2026-08-26 00:03 639232985300872416
816 ms 50.3.117.102