DNS response history for ns2.webkronz.com

ns2.webkronz.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-08. For this date, NameServerHistory found 40 DNS check records, 8 successful responses, 32 failed responses, and 1479 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.webkronz.com.
Records on Selected Date

40

Historical checks stored for this nameserver on selected date

Average Latency

1479 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-08 22:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.30.214.206

Most recently resolved hosting IP on selected date

Successful Responses

8

Checks that returned a measurable response

Failed Responses

32

Checks with no response or no returned latency

Failure Rate

80%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.webkronz.com

Showing DNS history for 2026-08-08 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
40 2026-08-08 22:48 639218252106422334
-
39 2026-08-08 21:11 639218194282616684
-
38 2026-08-08 19:34 639218135900313734
-
37 2026-08-08 17:58 639218078440804962
-
36 2026-08-08 16:23 639218021131612993
-
35 2026-08-08 14:47 639217963788814319
-
34 2026-08-08 13:12 639217906769667024
-
33 2026-08-08 11:38 639217850620659312
-
32 2026-08-08 11:24 639217841938624907
-
31 2026-08-08 11:09 639217833389546843
-
30 2026-08-08 10:55 639217824846173945
-
29 2026-08-08 10:03 639217793807292972
2010 ms 69.30.214.206
28 2026-08-08 09:49 639217785208951403
-
27 2026-08-08 09:35 639217776566534942
-
26 2026-08-08 09:20 639217767935139326
-
25 2026-08-08 08:29 639217737225367411
-
24 2026-08-08 08:15 639217728765093674
-
23 2026-08-08 08:01 639217720136905586
-
22 2026-08-08 07:46 639217711410853004
2009 ms 69.30.214.206
21 2026-08-08 06:54 639217680275549698
-
20 2026-08-08 06:40 639217671340563867
-
19 2026-08-08 06:25 639217662739829952
-
18 2026-08-08 06:10 639217654129395144
-
17 2026-08-08 05:19 639217623690502934
-
16 2026-08-08 05:05 639217615180184169
3512 ms 69.30.214.206
15 2026-08-08 04:51 639217606737293244
-
14 2026-08-08 04:37 639217598089858483
-
13 2026-08-08 03:45 639217567343169140
2008 ms 69.30.214.206
12 2026-08-08 03:31 639217558743892856
2008 ms 69.30.214.206
11 2026-08-08 03:17 639217550069823359
-
10 2026-08-08 03:02 639217541571663863
-
9 2026-08-08 02:00 639217510598671918
-
8 2026-08-08 01:46 639217501853904641
-
7 2026-08-08 01:30 639217492857464038
-
6 2026-08-08 01:16 639217483935810845
-
5 2026-08-08 01:01 639217475281344873
-
4 2026-08-08 00:47 639217466591266473
10 ms 69.30.214.206
3 2026-08-08 00:32 639217457842031506
-
2 2026-08-08 00:18 639217449192590684
28 ms 69.30.214.206
1 2026-08-08 00:03 639217440385817840
245 ms 69.30.214.206