DNS response history for la2.coronadosdtla.com

la2.coronadosdtla.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 26 DNS check records, 26 successful responses, 0 failed responses, and 691 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 la2.coronadosdtla.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

691 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.79.84.123

Most recently resolved hosting IP on selected date

Successful Responses

26

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 la2.coronadosdtla.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
26 2026-08-24 10:43 639231641791249939
855 ms 51.79.84.123
25 2026-08-24 10:27 639231631866211033
870 ms 51.79.84.123
24 2026-08-24 10:10 639231621644955316
871 ms 51.79.84.123
23 2026-08-24 09:53 639231611478799259
869 ms 51.79.84.123
22 2026-08-24 09:00 639231579923718211
575 ms 51.79.84.123
21 2026-08-24 08:44 639231569810702936
853 ms 51.79.84.123
20 2026-08-24 08:27 639231559762411619
873 ms 51.79.84.123
19 2026-08-24 08:10 639231549663595407
870 ms 51.79.84.123
18 2026-08-24 07:17 639231518076817246
862 ms 51.79.84.123
17 2026-08-24 07:01 639231508078650885
869 ms 51.79.84.123
16 2026-08-24 06:44 639231498210697093
238 ms 51.79.84.123
15 2026-08-24 06:28 639231488109699360
870 ms 51.79.84.123
14 2026-08-24 05:35 639231456772510692
900 ms 51.79.84.123
13 2026-08-24 05:19 639231447084631185
889 ms 51.79.84.123
12 2026-08-24 05:02 639231437208519473
878 ms 51.79.84.123
11 2026-08-24 04:46 639231427209627490
866 ms 51.79.84.123
10 2026-08-24 03:53 639231395791246644
864 ms 51.79.84.123
9 2026-08-24 03:37 639231386075551458
500 ms 51.79.84.123
8 2026-08-24 03:21 639231376208713791
869 ms 51.79.84.123
7 2026-08-24 03:04 639231366170589276
238 ms 51.79.84.123
6 2026-08-24 02:12 639231334732159368
130 ms 51.79.84.123
5 2026-08-24 01:55 639231325035670078
554 ms 51.79.84.123
4 2026-08-24 01:39 639231315132253837
868 ms 51.79.84.123
3 2026-08-24 01:22 639231305014280808
246 ms 51.79.84.123
2 2026-08-24 00:30 639231273779380675
133 ms 51.79.84.123
1 2026-08-24 00:14 639231264180839154
558 ms 51.79.84.123