DNS response history for ns2.correomc.com

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

39

Historical checks stored for this nameserver on selected date

Average Latency

345 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

34.176.176.98

Most recently resolved hosting IP on selected date

Successful Responses

39

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.correomc.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
39 2026-08-25 13:32 639232608016476376
408 ms 34.176.176.98
38 2026-08-25 13:14 639232597643611557
402 ms 34.176.176.98
37 2026-08-25 12:57 639232587225721862
404 ms 34.176.176.98
36 2026-08-25 12:40 639232576780683689
205 ms 34.176.176.98
35 2026-08-25 12:22 639232566381512620
407 ms 34.176.176.98
34 2026-08-25 12:05 639232556111768563
416 ms 34.176.176.98
33 2026-08-25 11:48 639232545839529039
229 ms 34.176.176.98
32 2026-08-25 11:31 639232535349285207
402 ms 34.176.176.98
31 2026-08-25 11:13 639232524938080723
417 ms 34.176.176.98
30 2026-08-25 10:19 639232492740373468
413 ms 34.176.176.98
29 2026-08-25 10:02 639232482235303141
203 ms 34.176.176.98
28 2026-08-25 09:45 639232471861770303
213 ms 34.176.176.98
27 2026-08-25 09:27 639232461630217327
404 ms 34.176.176.98
26 2026-08-25 09:10 639232451282965990
405 ms 34.176.176.98
25 2026-08-25 08:53 639232440814614938
407 ms 34.176.176.98
24 2026-08-25 08:36 639232430410720425
208 ms 34.176.176.98
23 2026-08-25 08:18 639232420003096185
402 ms 34.176.176.98
22 2026-08-25 08:01 639232409467287444
404 ms 34.176.176.98
21 2026-08-25 07:43 639232399077195997
414 ms 34.176.176.98
20 2026-08-25 07:26 639232388731528337
35 ms 34.176.176.98
19 2026-08-25 07:09 639232378288598612
2217 ms 34.176.176.98
18 2026-08-25 06:15 639232346196373643
265 ms 34.176.176.98
17 2026-08-25 05:58 639232336112370741
246 ms 34.176.176.98
16 2026-08-25 05:41 639232326146508970
199 ms 34.176.176.98
15 2026-08-25 05:25 639232316189381720
202 ms 34.176.176.98
14 2026-08-25 05:08 639232306217998913
9 ms 34.176.176.98
13 2026-08-25 04:52 639232296255744174
397 ms 34.176.176.98
12 2026-08-25 04:35 639232286095760789
201 ms 34.176.176.98
11 2026-08-25 04:18 639232276086186273
206 ms 34.176.176.98
10 2026-08-25 04:01 639232265900986425
215 ms 34.176.176.98
9 2026-08-25 03:44 639232255723518075
404 ms 34.176.176.98
8 2026-08-25 03:27 639232245484452890
217 ms 34.176.176.98
7 2026-08-25 03:10 639232235157175331
405 ms 34.176.176.98
6 2026-08-25 02:17 639232203197189095
198 ms 34.176.176.98
5 2026-08-25 02:00 639232192844564298
4 ms 34.176.176.98
4 2026-08-25 01:42 639232182496008942
409 ms 34.176.176.98
3 2026-08-25 01:25 639232172197053132
401 ms 34.176.176.98
2 2026-08-25 00:32 639232140250307418
204 ms 34.176.176.98
1 2026-08-25 00:15 639232129927860324
262 ms 34.176.176.98