DNS response history for ns2.shocking.com

ns2.shocking.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-27. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 1037 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.shocking.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

1037 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

38.247.141.170

Most recently resolved hosting IP on selected date

Successful Responses

29

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.shocking.com

Showing DNS history for 2026-08-27 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
29 2026-08-27 09:17 639234181105879568
271 ms 38.247.141.170
28 2026-08-27 09:00 639234170713214496
2130 ms 108.166.190.164
27 2026-08-27 08:42 639234160341037652
2254 ms 38.247.141.170
26 2026-08-27 08:25 639234149799404224
278 ms 38.247.141.170
25 2026-08-27 08:07 639234139553286469
272 ms 38.247.141.170
24 2026-08-27 07:14 639234107183588293
140 ms 108.166.190.164
23 2026-08-27 06:57 639234096905435724
268 ms 38.247.141.170
22 2026-08-27 06:39 639234086579410775
2179 ms 108.166.190.164
21 2026-08-27 06:22 639234076291157956
2136 ms 108.166.190.164
20 2026-08-27 06:05 639234065981939454
135 ms 38.247.141.170
19 2026-08-27 05:48 639234055548642997
2131 ms 108.166.190.164
18 2026-08-27 05:30 639234045267979603
266 ms 38.247.141.170
17 2026-08-27 05:13 639234034999717463
2127 ms 108.166.190.164
16 2026-08-27 04:56 639234024739225358
268 ms 38.247.141.170
15 2026-08-27 04:39 639234014311170162
273 ms 38.247.141.170
14 2026-08-27 04:22 639234003806017640
270 ms 38.247.141.170
13 2026-08-27 04:04 639233993356203030
269 ms 38.247.141.170
12 2026-08-27 03:11 639233961301716608
2180 ms 38.247.141.170
11 2026-08-27 02:53 639233950834200647
265 ms 38.247.141.170
10 2026-08-27 02:36 639233940431849026
271 ms 38.247.141.170
9 2026-08-27 02:19 639233930110596398
2128 ms 38.247.141.170
8 2026-08-27 02:01 639233919705434540
2179 ms 108.166.190.164
7 2026-08-27 01:44 639233909452807845
246 ms 38.247.141.170
6 2026-08-27 01:27 639233899096420820
245 ms 38.247.141.170
5 2026-08-27 01:10 639233888707824939
2122 ms 38.247.141.170
4 2026-08-27 00:52 639233878461203802
248 ms 38.247.141.170
3 2026-08-27 00:35 639233868060868209
2137 ms 38.247.141.170
2 2026-08-27 00:18 639233857450922991
2127 ms 108.166.190.164
1 2026-08-27 00:00 639233846871926285
247 ms 38.247.141.170