DNS response history for ns2.correosmype.com

ns2.correosmype.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, 29 successful responses, 1 failed responses, and 105 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.correosmype.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

105 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.93.110.135

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.correosmype.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:14 639232492740373468
12 ms 172.93.110.135
29 2026-08-25 09:57 639232482235303141
24 ms 172.93.110.135
28 2026-08-25 09:39 639232471861770303
19 ms 172.93.110.135
27 2026-08-25 09:22 639232461630217327
15 ms 172.93.110.135
26 2026-08-25 09:05 639232451282965990
39 ms 172.93.110.135
25 2026-08-25 08:48 639232440814614938
122 ms 172.93.110.135
24 2026-08-25 08:30 639232430410720425
12 ms 172.93.110.135
23 2026-08-25 08:13 639232420003096185
35 ms 172.93.110.135
22 2026-08-25 07:56 639232409467287444
178 ms 172.93.110.135
21 2026-08-25 07:38 639232399077195997
13 ms 172.93.110.135
20 2026-08-25 07:21 639232388731528337
9 ms 172.93.110.135
19 2026-08-25 07:04 639232378288598612
-
18 2026-08-25 06:10 639232346196373643
12 ms 172.93.110.135
17 2026-08-25 05:53 639232336112370741
36 ms 172.93.110.135
16 2026-08-25 05:37 639232326146508970
30 ms 172.93.110.135
15 2026-08-25 05:20 639232316189381720
18 ms 172.93.110.135
14 2026-08-25 05:04 639232306217998913
20 ms 172.93.110.135
13 2026-08-25 04:47 639232296255744174
17 ms 172.93.110.135
12 2026-08-25 04:30 639232286095760789
123 ms 172.93.110.135
11 2026-08-25 04:13 639232276086186273
23 ms 172.93.110.135
10 2026-08-25 03:56 639232265900986425
24 ms 172.93.110.135
9 2026-08-25 03:39 639232255723518075
2012 ms 172.93.110.135
8 2026-08-25 03:22 639232245484452890
38 ms 172.93.110.135
7 2026-08-25 03:05 639232235157175331
19 ms 172.93.110.135
6 2026-08-25 02:12 639232203197189095
25 ms 172.93.110.135
5 2026-08-25 01:55 639232192844564298
32 ms 172.93.110.135
4 2026-08-25 01:37 639232182496008942
48 ms 172.93.110.135
3 2026-08-25 01:20 639232172197053132
43 ms 172.93.110.135
2 2026-08-25 00:27 639232140250307418
15 ms 172.93.110.135
1 2026-08-25 00:10 639232129927860324
21 ms 172.93.110.135