DNS response history for ns2.peakbeak.com

ns2.peakbeak.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 28 DNS check records, 25 successful responses, 3 failed responses, and 3000 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.peakbeak.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

3000 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

165.140.69.238

Most recently resolved hosting IP on selected date

Successful Responses

25

Checks that returned a measurable response

Failed Responses

3

Checks with no response or no returned latency

Failure Rate

11%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.peakbeak.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
28 2026-08-26 09:03 639233308387917838
2013 ms 165.140.69.238
27 2026-08-26 08:46 639233297961740122
-
26 2026-08-26 08:28 639233287487159094
2009 ms 165.140.69.238
25 2026-08-26 08:11 639233276995531707
2141 ms 165.140.69.238
24 2026-08-26 07:53 639233266521568229
2007 ms 165.140.69.238
23 2026-08-26 07:36 639233256081047431
5137 ms 165.140.69.238
22 2026-08-26 06:41 639233223620132921
2135 ms 165.140.69.238
21 2026-08-26 06:24 639233213287814244
4009 ms 165.140.69.238
20 2026-08-26 06:07 639233202925983161
4131 ms 165.140.69.238
19 2026-08-26 05:50 639233192644780696
5148 ms 165.140.69.238
18 2026-08-26 05:32 639233182401183833
2131 ms 165.140.69.238
17 2026-08-26 05:16 639233172074181051
2008 ms 165.140.69.238
16 2026-08-26 04:58 639233161808421455
-
15 2026-08-26 04:41 639233151357344052
2033 ms 165.140.69.238
14 2026-08-26 04:24 639233141034116946
2031 ms 165.140.69.238
13 2026-08-26 04:07 639233130828334142
2137 ms 165.140.69.238
12 2026-08-26 03:49 639233120373450007
2129 ms 165.140.69.238
11 2026-08-26 03:32 639233110066216193
4009 ms 165.140.69.238
10 2026-08-26 02:39 639233078065410564
2008 ms 165.140.69.238
9 2026-08-26 02:22 639233067787457832
2143 ms 165.140.69.238
8 2026-08-26 02:04 639233057501801162
4140 ms 165.140.69.238
7 2026-08-26 01:47 639233047089431703
4008 ms 165.140.69.238
6 2026-08-26 01:30 639233036754790688
2171 ms 165.140.69.238
5 2026-08-26 01:13 639233026412602472
4008 ms 165.140.69.238
4 2026-08-26 00:55 639233016064066127
4150 ms 165.140.69.238
3 2026-08-26 00:38 639233005922655772
4009 ms 165.140.69.238
2 2026-08-26 00:21 639232995672256907
-
1 2026-08-26 00:04 639232985300872416
3148 ms 165.140.69.238