DNS response history for ns2.ohloyal.com

ns2.ohloyal.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-24. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 287 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.ohloyal.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

287 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.208.190.67

Most recently resolved hosting IP on selected date

Successful Responses

28

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.ohloyal.com

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
28 2026-08-24 11:48 639231683712487276
321 ms 74.208.190.67
27 2026-08-24 11:32 639231673513573868
6 ms 74.208.190.67
26 2026-08-24 10:38 639231641791249939
28 ms 74.208.190.67
25 2026-08-24 10:22 639231631866211033
3 ms 74.208.190.67
24 2026-08-24 10:05 639231621644955316
23 ms 74.208.190.67
23 2026-08-24 09:48 639231611478799259
5 ms 74.208.190.67
22 2026-08-24 08:56 639231579923718211
132 ms 74.208.190.67
21 2026-08-24 08:39 639231569810702936
337 ms 74.208.190.67
20 2026-08-24 08:22 639231559762411619
314 ms 74.208.190.67
19 2026-08-24 08:05 639231549663595407
308 ms 74.208.190.67
18 2026-08-24 07:12 639231518076817246
5 ms 74.208.190.67
17 2026-08-24 06:56 639231508078650885
323 ms 74.208.190.67
16 2026-08-24 06:39 639231498210697093
125 ms 74.208.190.67
15 2026-08-24 06:23 639231488109699360
8 ms 74.208.190.67
14 2026-08-24 05:30 639231456772510692
9 ms 74.208.190.67
13 2026-08-24 05:14 639231447084631185
144 ms 74.208.190.67
12 2026-08-24 04:58 639231437208519473
3 ms 74.208.190.67
11 2026-08-24 04:41 639231427209627490
318 ms 74.208.190.67
10 2026-08-24 03:48 639231395791246644
128 ms 74.208.190.67
9 2026-08-24 03:32 639231386075551458
2342 ms 74.208.190.67
8 2026-08-24 03:16 639231376208713791
158 ms 74.208.190.67
7 2026-08-24 02:59 639231366170589276
3 ms 74.208.190.67
6 2026-08-24 02:07 639231334732159368
326 ms 74.208.190.67
5 2026-08-24 01:51 639231325035670078
327 ms 74.208.190.67
4 2026-08-24 01:34 639231315132253837
172 ms 74.208.190.67
3 2026-08-24 01:18 639231305014280808
125 ms 74.208.190.67
2 2026-08-24 00:25 639231273779380675
2033 ms 74.208.190.67
1 2026-08-24 00:09 639231264180839154
4 ms 74.208.190.67