DNS response history for ns2.corelinkdc.net

ns2.corelinkdc.net 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 546 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.corelinkdc.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

546 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

67.21.172.198

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.corelinkdc.net

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
338 ms 67.21.172.198
29 2026-08-25 10:02 639232482235303141
588 ms 67.21.172.198
28 2026-08-25 09:45 639232471861770303
344 ms 67.21.172.198
27 2026-08-25 09:27 639232461630217327
584 ms 67.21.172.198
26 2026-08-25 09:10 639232451282965990
647 ms 67.21.172.198
25 2026-08-25 08:53 639232440814614938
663 ms 67.21.172.198
24 2026-08-25 08:36 639232430410720425
294 ms 67.21.172.198
23 2026-08-25 08:18 639232420003096185
317 ms 67.21.172.198
22 2026-08-25 08:01 639232409467287444
352 ms 67.21.172.198
21 2026-08-25 07:43 639232399077195997
4 ms 67.21.172.198
20 2026-08-25 07:26 639232388731528337
4 ms 67.21.172.198
19 2026-08-25 07:09 639232378288598612
283 ms 67.21.172.198
18 2026-08-25 06:15 639232346196373643
2138 ms 67.21.172.198
17 2026-08-25 05:58 639232336112370741
4 ms 67.21.172.198
16 2026-08-25 05:42 639232326146508970
4 ms 67.21.172.198
15 2026-08-25 05:25 639232316189381720
4 ms 67.21.172.198
14 2026-08-25 05:08 639232306217998913
219 ms 67.21.172.198
13 2026-08-25 04:52 639232296255744174
301 ms 67.21.172.198
12 2026-08-25 04:35 639232286095760789
316 ms 67.21.172.198
11 2026-08-25 04:18 639232276086186273
190 ms 67.21.172.198
10 2026-08-25 04:01 639232265900986425
611 ms 67.21.172.198
9 2026-08-25 03:44 639232255723518075
9 ms 67.21.172.198
8 2026-08-25 03:27 639232245484452890
308 ms 67.21.172.198
7 2026-08-25 03:10 639232235157175331
2233 ms 67.21.172.198
6 2026-08-25 02:17 639232203197189095
190 ms 67.21.172.198
5 2026-08-25 02:00 639232192844564298
190 ms 67.21.172.198
4 2026-08-25 01:42 639232182496008942
282 ms 67.21.172.198
3 2026-08-25 01:25 639232172197053132
389 ms 67.21.172.198
2 2026-08-25 00:32 639232140250307418
2245 ms 67.21.172.198
1 2026-08-25 00:15 639232129927860324
2316 ms 67.21.172.198