DNS response history for ns1.sanluisobispowebdesign.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

390 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

140.82.23.161

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 ns1.sanluisobispowebdesign.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
30 2026-08-25 10:18 639232492740373468
313 ms 140.82.23.161
29 2026-08-25 10:01 639232482235303141
298 ms 140.82.23.161
28 2026-08-25 09:43 639232471861770303
330 ms 140.82.23.161
27 2026-08-25 09:26 639232461630217327
322 ms 140.82.23.161
26 2026-08-25 09:09 639232451282965990
30 ms 140.82.23.161
25 2026-08-25 08:51 639232440814614938
332 ms 140.82.23.161
24 2026-08-25 08:34 639232430410720425
334 ms 140.82.23.161
23 2026-08-25 08:17 639232420003096185
315 ms 140.82.23.161
22 2026-08-25 07:59 639232409467287444
11 ms 140.82.23.161
21 2026-08-25 07:42 639232399077195997
318 ms 140.82.23.161
20 2026-08-25 07:24 639232388731528337
315 ms 140.82.23.161
19 2026-08-25 07:07 639232378288598612
336 ms 140.82.23.161
18 2026-08-25 06:13 639232346196373643
160 ms 140.82.23.161
17 2026-08-25 05:57 639232336112370741
321 ms 140.82.23.161
16 2026-08-25 05:40 639232326146508970
321 ms 140.82.23.161
15 2026-08-25 05:23 639232316189381720
327 ms 140.82.23.161
14 2026-08-25 05:07 639232306217998913
3 ms 140.82.23.161
13 2026-08-25 04:50 639232296255744174
318 ms 140.82.23.161
12 2026-08-25 04:33 639232286095760789
313 ms 140.82.23.161
11 2026-08-25 04:16 639232276086186273
311 ms 140.82.23.161
10 2026-08-25 04:00 639232265900986425
326 ms 140.82.23.161
9 2026-08-25 03:43 639232255723518075
157 ms 140.82.23.161
8 2026-08-25 03:26 639232245484452890
325 ms 140.82.23.161
7 2026-08-25 03:08 639232235157175331
2007 ms 140.82.23.161
6 2026-08-25 02:15 639232203197189095
320 ms 140.82.23.161
5 2026-08-25 01:58 639232192844564298
158 ms 140.82.23.161
4 2026-08-25 01:41 639232182496008942
312 ms 140.82.23.161
3 2026-08-25 01:23 639232172197053132
306 ms 140.82.23.161
2 2026-08-25 00:30 639232140250307418
306 ms 140.82.23.161
1 2026-08-25 00:13 639232129927860324
2153 ms 140.82.23.161