DNS response history for ns2.core2host.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

336 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.179.83.87

Most recently resolved hosting IP on selected date

Successful Responses

35

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.core2host.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
35 2026-08-25 12:20 639232566381512620
154 ms 66.179.83.87
34 2026-08-25 12:03 639232556111768563
163 ms 66.179.83.87
33 2026-08-25 11:46 639232545839529039
235 ms 66.179.83.87
32 2026-08-25 11:29 639232535349285207
324 ms 66.179.83.87
31 2026-08-25 11:11 639232524938080723
152 ms 66.179.83.87
30 2026-08-25 10:18 639232492740373468
168 ms 66.179.83.87
29 2026-08-25 10:01 639232482235303141
124 ms 66.179.83.87
28 2026-08-25 09:43 639232471861770303
165 ms 66.179.83.87
27 2026-08-25 09:26 639232461630217327
167 ms 66.179.83.87
26 2026-08-25 09:09 639232451282965990
161 ms 66.179.83.87
25 2026-08-25 08:51 639232440814614938
319 ms 66.179.83.87
24 2026-08-25 08:34 639232430410720425
159 ms 66.179.83.87
23 2026-08-25 08:17 639232420003096185
339 ms 66.179.83.87
22 2026-08-25 07:59 639232409467287444
329 ms 66.179.83.87
21 2026-08-25 07:42 639232399077195997
126 ms 66.179.83.87
20 2026-08-25 07:24 639232388731528337
127 ms 66.179.83.87
19 2026-08-25 07:07 639232378288598612
165 ms 66.179.83.87
18 2026-08-25 06:13 639232346196373643
341 ms 66.179.83.87
17 2026-08-25 05:56 639232336112370741
317 ms 66.179.83.87
16 2026-08-25 05:40 639232326146508970
126 ms 66.179.83.87
15 2026-08-25 05:23 639232316189381720
330 ms 66.179.83.87
14 2026-08-25 05:07 639232306217998913
33 ms 66.179.83.87
13 2026-08-25 04:50 639232296255744174
159 ms 66.179.83.87
12 2026-08-25 04:33 639232286095760789
170 ms 66.179.83.87
11 2026-08-25 04:16 639232276086186273
322 ms 66.179.83.87
10 2026-08-25 04:00 639232265900986425
329 ms 66.179.83.87
9 2026-08-25 03:43 639232255723518075
310 ms 66.179.83.87
8 2026-08-25 03:26 639232245484452890
2125 ms 66.179.83.87
7 2026-08-25 03:08 639232235157175331
325 ms 66.179.83.87
6 2026-08-25 02:15 639232203197189095
132 ms 66.179.83.87
5 2026-08-25 01:58 639232192844564298
2237 ms 66.179.83.87
4 2026-08-25 01:41 639232182496008942
145 ms 66.179.83.87
3 2026-08-25 01:23 639232172197053132
327 ms 66.179.83.87
2 2026-08-25 00:30 639232140250307418
313 ms 66.179.83.87
1 2026-08-25 00:13 639232129927860324
327 ms 66.179.83.87