DNS response history for ns3.nanolash.com

ns3.nanolash.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 24 DNS check records, 24 successful responses, 0 failed responses, and 378 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 ns3.nanolash.com.
Records on Selected Date

24

Historical checks stored for this nameserver on selected date

Average Latency

378 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 07:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

54.38.67.123

Most recently resolved hosting IP on selected date

Successful Responses

24

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 ns3.nanolash.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
24 2026-08-26 07:59 639233276995531707
34 ms 54.38.67.123
23 2026-08-26 07:41 639233266521568229
5 ms 54.38.67.123
22 2026-08-26 07:24 639233256081047431
19 ms 54.38.67.123
21 2026-08-26 06:30 639233223620132921
59 ms 54.38.67.123
20 2026-08-26 06:13 639233213287814244
2033 ms 54.38.67.123
19 2026-08-26 05:55 639233202925983161
29 ms 54.38.67.123
18 2026-08-26 05:38 639233192644780696
12 ms 54.38.67.123
17 2026-08-26 05:21 639233182401183833
2043 ms 54.38.67.123
16 2026-08-26 05:04 639233172074181051
49 ms 54.38.67.123
15 2026-08-26 04:47 639233161808421455
8 ms 54.38.67.123
14 2026-08-26 04:29 639233151357344052
2166 ms 54.38.67.123
13 2026-08-26 04:12 639233141034116946
202 ms 54.38.67.123
12 2026-08-26 03:55 639233130828334142
24 ms 54.38.67.123
11 2026-08-26 03:38 639233120373450007
8 ms 54.38.67.123
10 2026-08-26 03:21 639233110066216193
2033 ms 54.38.67.123
9 2026-08-26 02:27 639233078065410564
166 ms 54.38.67.123
8 2026-08-26 02:10 639233067787457832
30 ms 54.38.67.123
7 2026-08-26 01:53 639233057501801162
45 ms 54.38.67.123
6 2026-08-26 01:36 639233047089431703
41 ms 54.38.67.123
5 2026-08-26 01:18 639233036754790688
17 ms 54.38.67.123
4 2026-08-26 01:01 639233026412602472
13 ms 54.38.67.123
3 2026-08-26 00:44 639233016064066127
19 ms 54.38.67.123
2 2026-08-26 00:27 639233005922655772
4 ms 54.38.67.123
1 2026-08-26 00:10 639232995672256907
22 ms 54.38.67.123