DNS response history for ns2.sharpkey.com

ns2.sharpkey.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 33 DNS check records, 32 successful responses, 1 failed responses, and 236 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.sharpkey.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

236 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

96.44.156.178

Most recently resolved hosting IP on selected date

Successful Responses

32

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.sharpkey.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
33 2026-08-25 11:39 639232545839529039
40 ms 96.44.156.178
32 2026-08-25 11:21 639232535349285207
17 ms 96.44.156.178
31 2026-08-25 11:04 639232524938080723
21 ms 96.44.156.178
30 2026-08-25 10:10 639232492740373468
101 ms 96.44.156.178
29 2026-08-25 09:53 639232482235303141
2023 ms 96.44.156.178
28 2026-08-25 09:35 639232471861770303
158 ms 96.44.156.178
27 2026-08-25 09:18 639232461630217327
50 ms 96.44.156.178
26 2026-08-25 09:01 639232451282965990
20 ms 96.44.156.178
25 2026-08-25 08:44 639232440814614938
33 ms 96.44.156.178
24 2026-08-25 08:26 639232430410720425
38 ms 96.44.156.178
23 2026-08-25 08:09 639232420003096185
2023 ms 96.44.156.178
22 2026-08-25 07:51 639232409467287444
21 ms 96.44.156.178
21 2026-08-25 07:34 639232399077195997
87 ms 96.44.156.178
20 2026-08-25 07:17 639232388731528337
41 ms 96.44.156.178
19 2026-08-25 07:00 639232378288598612
45 ms 96.44.156.178
18 2026-08-25 06:06 639232346196373643
30 ms 96.44.156.178
17 2026-08-25 05:49 639232336112370741
53 ms 96.44.156.178
16 2026-08-25 05:32 639232326146508970
30 ms 96.44.156.178
15 2026-08-25 05:16 639232316189381720
16 ms 96.44.156.178
14 2026-08-25 04:59 639232306217998913
32 ms 96.44.156.178
13 2026-08-25 04:43 639232296255744174
32 ms 96.44.156.178
12 2026-08-25 04:26 639232286095760789
33 ms 96.44.156.178
11 2026-08-25 04:09 639232276086186273
27 ms 96.44.156.178
10 2026-08-25 03:52 639232265900986425
56 ms 96.44.156.178
9 2026-08-25 03:35 639232255723518075
2036 ms 96.44.156.178
8 2026-08-25 03:18 639232245484452890
156 ms 96.44.156.178
7 2026-08-25 03:01 639232235157175331
-
6 2026-08-25 02:08 639232203197189095
17 ms 96.44.156.178
5 2026-08-25 01:50 639232192844564298
60 ms 96.44.156.178
4 2026-08-25 01:33 639232182496008942
31 ms 96.44.156.178
3 2026-08-25 01:16 639232172197053132
46 ms 96.44.156.178
2 2026-08-25 00:23 639232140250307418
62 ms 96.44.156.178
1 2026-08-25 00:05 639232129927860324
131 ms 96.44.156.178