DNS response history for ns2.3kserver4.com

ns2.3kserver4.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-30. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 252 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.3kserver4.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

252 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.170.47.76

Most recently resolved hosting IP on selected date

Successful Responses

38

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.3kserver4.com

Showing DNS history for 2026-08-30 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
38 2026-08-30 12:11 639236878057367680
5 ms 108.170.47.76
37 2026-08-30 11:54 639236867916029489
317 ms 108.170.47.76
36 2026-08-30 11:37 639236858088772005
309 ms 108.170.47.76
35 2026-08-30 11:21 639236848158742395
4 ms 108.170.47.76
34 2026-08-30 11:04 639236838137395574
321 ms 108.170.47.76
33 2026-08-30 10:47 639236827967386881
320 ms 108.170.47.76
32 2026-08-30 10:30 639236817708615077
311 ms 108.170.47.76
31 2026-08-30 09:37 639236785770651804
311 ms 108.170.47.76
30 2026-08-30 09:20 639236775820686373
318 ms 108.170.47.76
29 2026-08-30 09:04 639236765768339082
314 ms 108.170.47.76
28 2026-08-30 08:47 639236755602384085
312 ms 108.170.47.76
27 2026-08-30 08:30 639236745600094925
309 ms 108.170.47.76
26 2026-08-30 08:13 639236735311262753
310 ms 108.170.47.76
25 2026-08-30 07:56 639236724996745235
3 ms 108.170.47.76
24 2026-08-30 07:39 639236714839899761
324 ms 108.170.47.76
23 2026-08-30 07:22 639236704748431488
307 ms 108.170.47.76
22 2026-08-30 07:05 639236694430128550
4 ms 108.170.47.76
21 2026-08-30 06:48 639236684143292417
3 ms 108.170.47.76
20 2026-08-30 06:31 639236673972499943
317 ms 108.170.47.76
19 2026-08-30 05:37 639236642126522802
313 ms 108.170.47.76
18 2026-08-30 05:21 639236632183518198
331 ms 108.170.47.76
17 2026-08-30 05:04 639236622289312589
322 ms 108.170.47.76
16 2026-08-30 04:48 639236612490676525
304 ms 108.170.47.76
15 2026-08-30 04:31 639236602582494852
319 ms 108.170.47.76
14 2026-08-30 04:15 639236592511706469
309 ms 108.170.47.76
13 2026-08-30 03:58 639236582441006869
319 ms 108.170.47.76
12 2026-08-30 03:41 639236572478785089
310 ms 108.170.47.76
11 2026-08-30 03:25 639236562556749999
157 ms 108.170.47.76
10 2026-08-30 03:08 639236552353482281
3 ms 108.170.47.76
9 2026-08-30 02:51 639236542188881607
3 ms 108.170.47.76
8 2026-08-30 02:34 639236531885440105
308 ms 108.170.47.76
7 2026-08-30 01:40 639236499922985383
303 ms 108.170.47.76
6 2026-08-30 01:24 639236489713594431
311 ms 108.170.47.76
5 2026-08-30 01:07 639236479750443901
317 ms 108.170.47.76
4 2026-08-30 00:50 639236469719936375
304 ms 108.170.47.76
3 2026-08-30 00:33 639236459579244885
310 ms 108.170.47.76
2 2026-08-30 00:17 639236449582837549
309 ms 108.170.47.76
1 2026-08-30 00:00 639236439461653110
314 ms 108.170.47.76