DNS response history for ns2.elcomsantiago.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

202 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

178.33.1.233

Most recently resolved hosting IP on selected date

Successful Responses

37

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.elcomsantiago.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
37 2026-08-25 12:46 639232587225721862
48 ms 178.33.1.233
36 2026-08-25 12:29 639232576780683689
78 ms 178.33.1.233
35 2026-08-25 12:11 639232566381512620
43 ms 178.33.1.233
34 2026-08-25 11:54 639232556111768563
57 ms 178.33.1.233
33 2026-08-25 11:37 639232545839529039
18 ms 178.33.1.233
32 2026-08-25 11:20 639232535349285207
38 ms 178.33.1.233
31 2026-08-25 11:02 639232524938080723
37 ms 178.33.1.233
30 2026-08-25 10:09 639232492740373468
2026 ms 178.33.1.233
29 2026-08-25 09:51 639232482235303141
23 ms 178.33.1.233
28 2026-08-25 09:34 639232471861770303
34 ms 178.33.1.233
27 2026-08-25 09:17 639232461630217327
32 ms 178.33.1.233
26 2026-08-25 09:00 639232451282965990
39 ms 178.33.1.233
25 2026-08-25 08:42 639232440814614938
38 ms 178.33.1.233
24 2026-08-25 08:25 639232430410720425
2010 ms 178.33.1.233
23 2026-08-25 08:07 639232420003096185
34 ms 178.33.1.233
22 2026-08-25 07:50 639232409467287444
51 ms 178.33.1.233
21 2026-08-25 07:33 639232399077195997
2053 ms 178.33.1.233
20 2026-08-25 07:15 639232388731528337
89 ms 178.33.1.233
19 2026-08-25 06:58 639232378288598612
39 ms 178.33.1.233
18 2026-08-25 06:04 639232346196373643
39 ms 178.33.1.233
17 2026-08-25 05:48 639232336112370741
32 ms 178.33.1.233
16 2026-08-25 05:31 639232326146508970
30 ms 178.33.1.233
15 2026-08-25 05:14 639232316189381720
47 ms 178.33.1.233
14 2026-08-25 04:58 639232306217998913
34 ms 178.33.1.233
13 2026-08-25 04:41 639232296255744174
7 ms 178.33.1.233
12 2026-08-25 04:24 639232286095760789
44 ms 178.33.1.233
11 2026-08-25 04:08 639232276086186273
37 ms 178.33.1.233
10 2026-08-25 03:51 639232265900986425
32 ms 178.33.1.233
9 2026-08-25 03:34 639232255723518075
84 ms 178.33.1.233
8 2026-08-25 03:17 639232245484452890
33 ms 178.33.1.233
7 2026-08-25 02:59 639232235157175331
22 ms 178.33.1.233
6 2026-08-25 02:06 639232203197189095
39 ms 178.33.1.233
5 2026-08-25 01:49 639232192844564298
38 ms 178.33.1.233
4 2026-08-25 01:32 639232182496008942
43 ms 178.33.1.233
3 2026-08-25 01:14 639232172197053132
22 ms 178.33.1.233
2 2026-08-25 00:21 639232140250307418
33 ms 178.33.1.233
1 2026-08-25 00:04 639232129927860324
66 ms 178.33.1.233