DNS response history for dns2.s3m.cl

dns2.s3m.cl 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 38 DNS check records, 38 successful responses, 0 failed responses, and 463 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 dns2.s3m.cl.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

463 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

190.113.0.128

Most recently resolved hosting IP on selected date

Successful Responses

38

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 dns2.s3m.cl

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
38 2026-08-25 13:16 639232597643611557
458 ms 190.113.0.128
37 2026-08-25 12:59 639232587225721862
456 ms 190.113.0.128
36 2026-08-25 12:41 639232576780683689
454 ms 190.113.0.128
35 2026-08-25 12:24 639232566381512620
455 ms 190.113.0.128
34 2026-08-25 12:07 639232556111768563
459 ms 190.113.0.128
33 2026-08-25 11:50 639232545839529039
465 ms 190.113.0.128
32 2026-08-25 11:33 639232535349285207
457 ms 190.113.0.128
31 2026-08-25 11:15 639232524938080723
480 ms 190.113.0.128
30 2026-08-25 10:21 639232492740373468
457 ms 190.113.0.128
29 2026-08-25 10:04 639232482235303141
482 ms 190.113.0.128
28 2026-08-25 09:47 639232471861770303
452 ms 190.113.0.128
27 2026-08-25 09:29 639232461630217327
455 ms 190.113.0.128
26 2026-08-25 09:12 639232451282965990
454 ms 190.113.0.128
25 2026-08-25 08:55 639232440814614938
457 ms 190.113.0.128
24 2026-08-25 08:38 639232430410720425
479 ms 190.113.0.128
23 2026-08-25 08:20 639232420003096185
463 ms 190.113.0.128
22 2026-08-25 08:03 639232409467287444
460 ms 190.113.0.128
21 2026-08-25 07:45 639232399077195997
509 ms 190.113.0.128
20 2026-08-25 07:28 639232388731528337
462 ms 190.113.0.128
19 2026-08-25 07:11 639232378288598612
453 ms 190.113.0.128
18 2026-08-25 06:17 639232346196373643
458 ms 190.113.0.128
17 2026-08-25 06:00 639232336112370741
459 ms 190.113.0.128
16 2026-08-25 05:43 639232326146508970
455 ms 190.113.0.128
15 2026-08-25 05:27 639232316189381720
465 ms 190.113.0.128
14 2026-08-25 05:10 639232306217998913
497 ms 190.113.0.128
13 2026-08-25 04:54 639232296255744174
456 ms 190.113.0.128
12 2026-08-25 04:37 639232286095760789
461 ms 190.113.0.128
11 2026-08-25 04:20 639232276086186273
457 ms 190.113.0.128
10 2026-08-25 04:03 639232265900986425
452 ms 190.113.0.128
9 2026-08-25 03:46 639232255723518075
455 ms 190.113.0.128
8 2026-08-25 03:29 639232245484452890
461 ms 190.113.0.128
7 2026-08-25 03:12 639232235157175331
460 ms 190.113.0.128
6 2026-08-25 02:19 639232203197189095
454 ms 190.113.0.128
5 2026-08-25 02:02 639232192844564298
481 ms 190.113.0.128
4 2026-08-25 01:44 639232182496008942
458 ms 190.113.0.128
3 2026-08-25 01:27 639232172197053132
457 ms 190.113.0.128
2 2026-08-25 00:34 639232140250307418
474 ms 190.113.0.128
1 2026-08-25 00:17 639232129927860324
462 ms 190.113.0.128