DNS response history for ns1.langdaleplace.com

ns1.langdaleplace.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-25. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 341 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.langdaleplace.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

341 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

207.5.37.130

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.langdaleplace.com

Showing DNS history for 2026-08-25 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-25 12:22 639232566381512620
257 ms 207.5.37.130
34 2026-08-25 12:05 639232556111768563
259 ms 207.5.37.130
33 2026-08-25 11:48 639232545839529039
262 ms 207.5.37.130
32 2026-08-25 11:31 639232535349285207
258 ms 207.5.37.130
31 2026-08-25 11:13 639232524938080723
258 ms 207.5.37.130
30 2026-08-25 10:20 639232492740373468
258 ms 207.5.37.130
29 2026-08-25 10:02 639232482235303141
262 ms 207.5.37.130
28 2026-08-25 09:45 639232471861770303
263 ms 207.5.37.130
27 2026-08-25 09:28 639232461630217327
261 ms 207.5.37.130
26 2026-08-25 09:10 639232451282965990
271 ms 207.5.37.130
25 2026-08-25 08:53 639232440814614938
263 ms 207.5.37.130
24 2026-08-25 08:36 639232430410720425
264 ms 207.5.37.130
23 2026-08-25 08:18 639232420003096185
146 ms 207.5.37.130
22 2026-08-25 08:01 639232409467287444
256 ms 207.5.37.130
21 2026-08-25 07:44 639232399077195997
250 ms 207.5.37.130
20 2026-08-25 07:26 639232388731528337
254 ms 207.5.37.130
19 2026-08-25 07:09 639232378288598612
257 ms 207.5.37.130
18 2026-08-25 06:15 639232346196373643
124 ms 207.5.37.130
17 2026-08-25 05:58 639232336112370741
122 ms 207.5.37.130
16 2026-08-25 05:42 639232326146508970
249 ms 207.5.37.130
15 2026-08-25 05:25 639232316189381720
250 ms 207.5.37.130
14 2026-08-25 05:09 639232306217998913
161 ms 207.5.37.130
13 2026-08-25 04:52 639232296255744174
142 ms 207.5.37.130
12 2026-08-25 04:35 639232286095760789
248 ms 207.5.37.130
11 2026-08-25 04:18 639232276086186273
248 ms 207.5.37.130
10 2026-08-25 04:01 639232265900986425
246 ms 207.5.37.130
9 2026-08-25 03:45 639232255723518075
169 ms 207.5.37.130
8 2026-08-25 03:27 639232245484452890
245 ms 207.5.37.130
7 2026-08-25 03:10 639232235157175331
252 ms 207.5.37.130
6 2026-08-25 02:17 639232203197189095
132 ms 207.5.37.130
5 2026-08-25 02:00 639232192844564298
249 ms 207.5.37.130
4 2026-08-25 01:43 639232182496008942
256 ms 207.5.37.130
3 2026-08-25 01:25 639232172197053132
2136 ms 207.5.37.130
2 2026-08-25 00:32 639232140250307418
2149 ms 207.5.37.130
1 2026-08-25 00:15 639232129927860324
248 ms 207.5.37.130