DNS response history for ns2.timberlook.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

100 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

46.43.20.123

Most recently resolved hosting IP on selected date

Successful Responses

37

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.timberlook.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
37 2026-08-24 15:28 639231818080917481
19 ms 46.43.20.123
36 2026-08-24 15:11 639231807961539652
36 ms 46.43.20.123
35 2026-08-24 14:54 639231797631669865
80 ms 46.43.20.123
34 2026-08-24 14:01 639231765923559455
30 ms 46.43.20.123
33 2026-08-24 13:44 639231755868832964
47 ms 46.43.20.123
32 2026-08-24 13:27 639231745628278877
60 ms 46.43.20.123
31 2026-08-24 13:10 639231735407682062
94 ms 46.43.20.123
30 2026-08-24 12:17 639231703815441688
6 ms 46.43.20.123
29 2026-08-24 12:01 639231693747052549
51 ms 46.43.20.123
28 2026-08-24 11:44 639231683712487276
77 ms 46.43.20.123
27 2026-08-24 11:27 639231673513573868
5 ms 46.43.20.123
26 2026-08-24 10:34 639231641791249939
47 ms 46.43.20.123
25 2026-08-24 10:18 639231631866211033
74 ms 46.43.20.123
24 2026-08-24 10:01 639231621644955316
66 ms 46.43.20.123
23 2026-08-24 09:44 639231611478799259
53 ms 46.43.20.123
22 2026-08-24 08:51 639231579923718211
68 ms 46.43.20.123
21 2026-08-24 08:34 639231569810702936
41 ms 46.43.20.123
20 2026-08-24 08:17 639231559762411619
7 ms 46.43.20.123
19 2026-08-24 08:01 639231549663595407
89 ms 46.43.20.123
18 2026-08-24 07:08 639231518076817246
2 ms 46.43.20.123
17 2026-08-24 06:52 639231508078650885
18 ms 46.43.20.123
16 2026-08-24 06:35 639231498210697093
57 ms 46.43.20.123
15 2026-08-24 06:18 639231488109699360
86 ms 46.43.20.123
14 2026-08-24 05:26 639231456772510692
78 ms 46.43.20.123
13 2026-08-24 05:10 639231447084631185
29 ms 46.43.20.123
12 2026-08-24 04:53 639231437208519473
58 ms 46.43.20.123
11 2026-08-24 04:37 639231427209627490
54 ms 46.43.20.123
10 2026-08-24 03:44 639231395791246644
2047 ms 46.43.20.123
9 2026-08-24 03:28 639231386075551458
7 ms 46.43.20.123
8 2026-08-24 03:12 639231376208713791
57 ms 46.43.20.123
7 2026-08-24 02:55 639231366170589276
62 ms 46.43.20.123
6 2026-08-24 02:03 639231334732159368
14 ms 46.43.20.123
5 2026-08-24 01:46 639231325035670078
78 ms 46.43.20.123
4 2026-08-24 01:30 639231315132253837
3 ms 46.43.20.123
3 2026-08-24 01:13 639231305014280808
21 ms 46.43.20.123
2 2026-08-24 00:21 639231273779380675
64 ms 46.43.20.123
1 2026-08-24 00:05 639231264180839154
11 ms 46.43.20.123