DNS response history for ns2.coreswitch.net

ns2.coreswitch.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 35 DNS check records, 33 successful responses, 2 failed responses, and 300 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.coreswitch.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

300 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

141.138.201.203

Most recently resolved hosting IP on selected date

Successful Responses

33

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

6%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.coreswitch.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
35 2026-08-25 12:14 639232566381512620
31 ms 141.138.201.203
34 2026-08-25 11:56 639232556111768563
88 ms 141.138.201.203
33 2026-08-25 11:39 639232545839529039
2019 ms 141.138.201.203
32 2026-08-25 11:22 639232535349285207
157 ms 141.138.201.203
31 2026-08-25 11:05 639232524938080723
55 ms 141.138.201.203
30 2026-08-25 10:11 639232492740373468
38 ms 141.138.201.203
29 2026-08-25 09:54 639232482235303141
38 ms 141.138.201.203
28 2026-08-25 09:36 639232471861770303
48 ms 141.138.201.203
27 2026-08-25 09:19 639232461630217327
2121 ms 141.138.201.203
26 2026-08-25 09:02 639232451282965990
-
25 2026-08-25 08:44 639232440814614938
44 ms 141.138.201.203
24 2026-08-25 08:27 639232430410720425
44 ms 141.138.201.203
23 2026-08-25 08:10 639232420003096185
8 ms 141.138.201.203
22 2026-08-25 07:52 639232409467287444
24 ms 141.138.201.203
21 2026-08-25 07:35 639232399077195997
27 ms 141.138.201.203
20 2026-08-25 07:18 639232388731528337
153 ms 141.138.201.203
19 2026-08-25 07:00 639232378288598612
40 ms 141.138.201.203
18 2026-08-25 06:07 639232346196373643
2041 ms 141.138.201.203
17 2026-08-25 05:50 639232336112370741
101 ms 141.138.201.203
16 2026-08-25 05:33 639232326146508970
84 ms 141.138.201.203
15 2026-08-25 05:17 639232316189381720
53 ms 141.138.201.203
14 2026-08-25 05:00 639232306217998913
28 ms 141.138.201.203
13 2026-08-25 04:44 639232296255744174
27 ms 141.138.201.203
12 2026-08-25 04:27 639232286095760789
39 ms 141.138.201.203
11 2026-08-25 04:10 639232276086186273
2033 ms 141.138.201.203
10 2026-08-25 03:53 639232265900986425
32 ms 141.138.201.203
9 2026-08-25 03:36 639232255723518075
42 ms 141.138.201.203
8 2026-08-25 03:19 639232245484452890
-
7 2026-08-25 03:02 639232235157175331
46 ms 141.138.201.203
6 2026-08-25 02:08 639232203197189095
40 ms 141.138.201.203
5 2026-08-25 01:51 639232192844564298
84 ms 141.138.201.203
4 2026-08-25 01:34 639232182496008942
142 ms 141.138.201.203
3 2026-08-25 01:17 639232172197053132
38 ms 141.138.201.203
2 2026-08-25 00:23 639232140250307418
67 ms 141.138.201.203
1 2026-08-25 00:06 639232129927860324
64 ms 141.138.201.203