DNS response history for ns2.locksmithpelhammanor.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

593 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

135.148.106.112

Most recently resolved hosting IP on selected date

Successful Responses

30

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.locksmithpelhammanor.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
30 2026-08-24 12:23 639231703815441688
205 ms 135.148.106.112
29 2026-08-24 12:07 639231693747052549
206 ms 135.148.106.112
28 2026-08-24 11:50 639231683712487276
158 ms 135.148.106.112
27 2026-08-24 11:33 639231673513573868
2128 ms 135.148.106.112
26 2026-08-24 10:40 639231641791249939
104 ms 135.148.106.112
25 2026-08-24 10:23 639231631866211033
208 ms 135.148.106.112
24 2026-08-24 10:07 639231621644955316
210 ms 135.148.106.112
23 2026-08-24 09:50 639231611478799259
107 ms 135.148.106.112
22 2026-08-24 08:57 639231579923718211
240 ms 135.148.106.112
21 2026-08-24 08:40 639231569810702936
3 ms 135.148.106.112
20 2026-08-24 08:23 639231559762411619
208 ms 135.148.106.112
19 2026-08-24 08:06 639231549663595407
209 ms 135.148.106.112
18 2026-08-24 07:14 639231518076817246
116 ms 135.148.106.112
17 2026-08-24 06:57 639231508078650885
3 ms 135.148.106.112
16 2026-08-24 06:41 639231498210697093
207 ms 135.148.106.112
15 2026-08-24 06:24 639231488109699360
2101 ms 135.148.106.112
14 2026-08-24 05:32 639231456772510692
103 ms 135.148.106.112
13 2026-08-24 05:16 639231447084631185
100 ms 135.148.106.112
12 2026-08-24 04:59 639231437208519473
106 ms 135.148.106.112
11 2026-08-24 04:42 639231427209627490
2101 ms 135.148.106.112
10 2026-08-24 03:50 639231395791246644
98 ms 135.148.106.112
9 2026-08-24 03:34 639231386075551458
205 ms 135.148.106.112
8 2026-08-24 03:18 639231376208713791
130 ms 135.148.106.112
7 2026-08-24 03:01 639231366170589276
123 ms 135.148.106.112
6 2026-08-24 02:08 639231334732159368
2103 ms 135.148.106.112
5 2026-08-24 01:52 639231325035670078
4204 ms 135.148.106.112
4 2026-08-24 01:36 639231315132253837
2100 ms 135.148.106.112
3 2026-08-24 01:19 639231305014280808
6 ms 135.148.106.112
2 2026-08-24 00:27 639231273779380675
3 ms 135.148.106.112
1 2026-08-24 00:11 639231264180839154
3 ms 135.148.106.112