DNS response history for ns2.correodmm.com

ns2.correodmm.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 439 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.correodmm.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

439 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

72.249.60.180

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 ns2.correodmm.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:19 639232492740373468
2166 ms 72.249.60.180
29 2026-08-25 10:02 639232482235303141
142 ms 72.249.60.180
28 2026-08-25 09:44 639232471861770303
295 ms 72.249.60.180
27 2026-08-25 09:27 639232461630217327
150 ms 72.249.60.180
26 2026-08-25 09:10 639232451282965990
285 ms 72.249.60.180
25 2026-08-25 08:52 639232440814614938
293 ms 72.249.60.180
24 2026-08-25 08:35 639232430410720425
299 ms 72.249.60.180
23 2026-08-25 08:18 639232420003096185
282 ms 72.249.60.180
22 2026-08-25 08:00 639232409467287444
298 ms 72.249.60.180
21 2026-08-25 07:43 639232399077195997
288 ms 72.249.60.180
20 2026-08-25 07:26 639232388731528337
147 ms 72.249.60.180
19 2026-08-25 07:08 639232378288598612
311 ms 72.249.60.180
18 2026-08-25 06:15 639232346196373643
421 ms 72.249.60.180
17 2026-08-25 05:58 639232336112370741
284 ms 72.249.60.180
16 2026-08-25 05:41 639232326146508970
299 ms 72.249.60.180
15 2026-08-25 05:24 639232316189381720
299 ms 72.249.60.180
14 2026-08-25 05:08 639232306217998913
149 ms 72.249.60.180
13 2026-08-25 04:51 639232296255744174
286 ms 72.249.60.180
12 2026-08-25 04:34 639232286095760789
138 ms 72.249.60.180
11 2026-08-25 04:18 639232276086186273
129 ms 72.249.60.180
10 2026-08-25 04:01 639232265900986425
161 ms 72.249.60.180
9 2026-08-25 03:44 639232255723518075
8 ms 72.249.60.180
8 2026-08-25 03:27 639232245484452890
286 ms 72.249.60.180
7 2026-08-25 03:10 639232235157175331
2163 ms 72.249.60.180
6 2026-08-25 02:16 639232203197189095
2249 ms 72.249.60.180
5 2026-08-25 01:59 639232192844564298
307 ms 72.249.60.180
4 2026-08-25 01:42 639232182496008942
293 ms 72.249.60.180
3 2026-08-25 01:25 639232172197053132
140 ms 72.249.60.180
2 2026-08-25 00:31 639232140250307418
300 ms 72.249.60.180
1 2026-08-25 00:14 639232129927860324
291 ms 72.249.60.180