DNS response history for ns1.ohlcx.app

ns1.ohlcx.app 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 35 DNS check records, 35 successful responses, 0 failed responses, and 285 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 ns1.ohlcx.app.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

285 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.208.156.159

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns1.ohlcx.app

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
35 2026-08-26 11:38 639233403515141099
327 ms 74.208.156.159
34 2026-08-26 10:43 639233370841350248
131 ms 74.208.156.159
33 2026-08-26 10:26 639233360361507238
3 ms 74.208.156.159
32 2026-08-26 10:09 639233350067824371
3 ms 74.208.156.159
31 2026-08-26 09:51 639233339545274518
4 ms 74.208.156.159
30 2026-08-26 09:34 639233329214918079
149 ms 74.208.156.159
29 2026-08-26 09:17 639233318749762337
342 ms 74.208.156.159
28 2026-08-26 08:59 639233308387917838
327 ms 74.208.156.159
27 2026-08-26 08:42 639233297961740122
157 ms 74.208.156.159
26 2026-08-26 08:25 639233287487159094
343 ms 74.208.156.159
25 2026-08-26 08:07 639233276995531707
173 ms 74.208.156.159
24 2026-08-26 07:50 639233266521568229
420 ms 74.208.156.159
23 2026-08-26 07:32 639233256081047431
315 ms 74.208.156.159
22 2026-08-26 06:38 639233223620132921
318 ms 74.208.156.159
21 2026-08-26 06:21 639233213287814244
321 ms 74.208.156.159
20 2026-08-26 06:04 639233202925983161
167 ms 74.208.156.159
19 2026-08-26 05:46 639233192644780696
2238 ms 74.208.156.159
18 2026-08-26 05:29 639233182401183833
320 ms 74.208.156.159
17 2026-08-26 05:12 639233172074181051
159 ms 74.208.156.159
16 2026-08-26 04:55 639233161808421455
158 ms 74.208.156.159
15 2026-08-26 04:38 639233151357344052
337 ms 74.208.156.159
14 2026-08-26 04:20 639233141034116946
328 ms 74.208.156.159
13 2026-08-26 04:03 639233130828334142
315 ms 74.208.156.159
12 2026-08-26 03:46 639233120373450007
332 ms 74.208.156.159
11 2026-08-26 03:29 639233110066216193
323 ms 74.208.156.159
10 2026-08-26 02:35 639233078065410564
337 ms 74.208.156.159
9 2026-08-26 02:18 639233067787457832
328 ms 74.208.156.159
8 2026-08-26 02:01 639233057501801162
9 ms 74.208.156.159
7 2026-08-26 01:44 639233047089431703
9 ms 74.208.156.159
6 2026-08-26 01:27 639233036754790688
309 ms 74.208.156.159
5 2026-08-26 01:10 639233026412602472
363 ms 74.208.156.159
4 2026-08-26 00:52 639233016064066127
130 ms 74.208.156.159
3 2026-08-26 00:35 639233005922655772
164 ms 74.208.156.159
2 2026-08-26 00:18 639232995672256907
9 ms 74.208.156.159
1 2026-08-26 00:01 639232985300872416
321 ms 74.208.156.159