DNS response history for ns2.corescoms.org

ns2.corescoms.org 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 47 DNS check records, 15 successful responses, 32 failed responses, and 220 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.corescoms.org.
Records on Selected Date

47

Historical checks stored for this nameserver on selected date

Average Latency

220 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 16:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

31.7.59.144

Most recently resolved hosting IP on selected date

Successful Responses

15

Checks that returned a measurable response

Failed Responses

32

Checks with no response or no returned latency

Failure Rate

68%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.corescoms.org

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
47 2026-08-25 16:14 639232703065318207
142 ms 31.7.59.144
46 2026-08-25 15:56 639232692629559470
9 ms 31.7.59.144
45 2026-08-25 15:39 639232682238836475
258 ms 31.7.59.144
44 2026-08-25 15:22 639232671787004306
147 ms 31.7.59.144
43 2026-08-25 14:27 639232638994329666
143 ms 31.7.59.144
42 2026-08-25 14:10 639232628614783237
24 ms 31.7.59.144
41 2026-08-25 13:52 639232618360728578
271 ms 31.7.59.144
40 2026-08-25 13:35 639232608016476376
8 ms 31.7.59.144
39 2026-08-25 13:18 639232597643611557
1774 ms 31.7.59.144
38 2026-08-25 13:01 639232587225721862
265 ms 31.7.59.144
37 2026-08-25 12:43 639232576780683689
9 ms 31.7.59.144
36 2026-08-25 12:26 639232566381512620
7 ms 31.7.59.144
35 2026-08-25 12:09 639232556111768563
168 ms 31.7.59.144
34 2026-08-25 11:51 639232545839529039
37 ms 31.7.59.144
33 2026-08-25 11:34 639232535349285207
38 ms 31.7.59.144
32 2026-08-25 11:17 639232524938080723
-
31 2026-08-25 10:23 639232492740373468
-
30 2026-08-25 10:06 639232482235303141
-
29 2026-08-25 09:48 639232471861770303
-
28 2026-08-25 09:31 639232461630217327
-
27 2026-08-25 09:14 639232451282965990
-
26 2026-08-25 08:57 639232440814614938
-
25 2026-08-25 08:39 639232430410720425
-
24 2026-08-25 08:22 639232420003096185
-
23 2026-08-25 08:05 639232409467287444
-
22 2026-08-25 07:47 639232399077195997
-
21 2026-08-25 07:30 639232388731528337
-
20 2026-08-25 07:13 639232378288598612
-
19 2026-08-25 06:19 639232346196373643
-
18 2026-08-25 06:02 639232336112370741
-
17 2026-08-25 05:45 639232326146508970
-
16 2026-08-25 05:28 639232316189381720
-
15 2026-08-25 05:12 639232306217998913
-
14 2026-08-25 04:55 639232296255744174
-
13 2026-08-25 04:38 639232286095760789
-
12 2026-08-25 04:22 639232276086186273
-
11 2026-08-25 04:05 639232265900986425
-
10 2026-08-25 03:48 639232255723518075
-
9 2026-08-25 03:31 639232245484452890
-
8 2026-08-25 03:14 639232235157175331
-
7 2026-08-25 02:20 639232203197189095
-
6 2026-08-25 02:03 639232192844564298
-
5 2026-08-25 01:46 639232182496008942
-
4 2026-08-25 01:29 639232172197053132
-
3 2026-08-25 00:35 639232140250307418
-
2 2026-08-25 00:19 639232129927860324
-
1 2026-08-25 00:01 639232119551972438
-