DNS response history for ns2.hospitallapiedad.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

496 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

166.62.119.96

Most recently resolved hosting IP on selected date

Successful Responses

34

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.hospitallapiedad.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
34 2026-08-25 12:03 639232556111768563
315 ms 166.62.119.96
33 2026-08-25 11:46 639232545839529039
169 ms 166.62.119.96
32 2026-08-25 11:29 639232535349285207
336 ms 166.62.119.96
31 2026-08-25 11:12 639232524938080723
318 ms 166.62.119.96
30 2026-08-25 10:18 639232492740373468
308 ms 166.62.119.96
29 2026-08-25 10:01 639232482235303141
318 ms 166.62.119.96
28 2026-08-25 09:43 639232471861770303
318 ms 166.62.119.96
27 2026-08-25 09:26 639232461630217327
2156 ms 166.62.119.96
26 2026-08-25 09:09 639232451282965990
2208 ms 166.62.119.96
25 2026-08-25 08:51 639232440814614938
160 ms 166.62.119.96
24 2026-08-25 08:34 639232430410720425
4 ms 166.62.119.96
23 2026-08-25 08:17 639232420003096185
327 ms 166.62.119.96
22 2026-08-25 07:59 639232409467287444
316 ms 166.62.119.96
21 2026-08-25 07:42 639232399077195997
326 ms 166.62.119.96
20 2026-08-25 07:25 639232388731528337
324 ms 166.62.119.96
19 2026-08-25 07:07 639232378288598612
307 ms 166.62.119.96
18 2026-08-25 06:14 639232346196373643
315 ms 166.62.119.96
17 2026-08-25 05:57 639232336112370741
323 ms 166.62.119.96
16 2026-08-25 05:40 639232326146508970
2162 ms 166.62.119.96
15 2026-08-25 05:23 639232316189381720
2185 ms 166.62.119.96
14 2026-08-25 05:07 639232306217998913
2 ms 166.62.119.96
13 2026-08-25 04:50 639232296255744174
312 ms 166.62.119.96
12 2026-08-25 04:33 639232286095760789
309 ms 166.62.119.96
11 2026-08-25 04:16 639232276086186273
309 ms 166.62.119.96
10 2026-08-25 04:00 639232265900986425
155 ms 166.62.119.96
9 2026-08-25 03:43 639232255723518075
184 ms 166.62.119.96
8 2026-08-25 03:26 639232245484452890
325 ms 166.62.119.96
7 2026-08-25 03:09 639232235157175331
314 ms 166.62.119.96
6 2026-08-25 02:15 639232203197189095
317 ms 166.62.119.96
5 2026-08-25 01:58 639232192844564298
345 ms 166.62.119.96
4 2026-08-25 01:41 639232182496008942
317 ms 166.62.119.96
3 2026-08-25 01:24 639232172197053132
319 ms 166.62.119.96
2 2026-08-25 00:30 639232140250307418
312 ms 166.62.119.96
1 2026-08-25 00:13 639232129927860324
160 ms 166.62.119.96