DNS response history for ns2.kroese.frl

ns2.kroese.frl 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-24. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 242 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.kroese.frl.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

242 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.203.140.122

Most recently resolved hosting IP on selected date

Successful Responses

32

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.kroese.frl

Showing DNS history for 2026-08-24 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
32 2026-08-24 13:30 639231745628278877
50 ms 116.203.140.122
31 2026-08-24 13:12 639231735407682062
47 ms 116.203.140.122
30 2026-08-24 12:20 639231703815441688
58 ms 116.203.140.122
29 2026-08-24 12:03 639231693747052549
58 ms 116.203.140.122
28 2026-08-24 11:46 639231683712487276
142 ms 116.203.140.122
27 2026-08-24 11:29 639231673513573868
34 ms 116.203.140.122
26 2026-08-24 10:36 639231641791249939
38 ms 116.203.140.122
25 2026-08-24 10:20 639231631866211033
30 ms 116.203.140.122
24 2026-08-24 10:03 639231621644955316
41 ms 116.203.140.122
23 2026-08-24 09:46 639231611478799259
41 ms 116.203.140.122
22 2026-08-24 08:53 639231579923718211
64 ms 116.203.140.122
21 2026-08-24 08:37 639231569810702936
31 ms 116.203.140.122
20 2026-08-24 08:20 639231559762411619
41 ms 116.203.140.122
19 2026-08-24 08:03 639231549663595407
51 ms 116.203.140.122
18 2026-08-24 07:10 639231518076817246
63 ms 116.203.140.122
17 2026-08-24 06:54 639231508078650885
50 ms 116.203.140.122
16 2026-08-24 06:37 639231498210697093
85 ms 116.203.140.122
15 2026-08-24 06:21 639231488109699360
63 ms 116.203.140.122
14 2026-08-24 05:28 639231456772510692
2056 ms 116.203.140.122
13 2026-08-24 05:12 639231447084631185
36 ms 116.203.140.122
12 2026-08-24 04:56 639231437208519473
2041 ms 116.203.140.122
11 2026-08-24 04:39 639231427209627490
94 ms 116.203.140.122
10 2026-08-24 03:46 639231395791246644
2026 ms 116.203.140.122
9 2026-08-24 03:30 639231386075551458
74 ms 116.203.140.122
8 2026-08-24 03:14 639231376208713791
39 ms 116.203.140.122
7 2026-08-24 02:57 639231366170589276
31 ms 116.203.140.122
6 2026-08-24 02:05 639231334732159368
130 ms 116.203.140.122
5 2026-08-24 01:49 639231325035670078
39 ms 116.203.140.122
4 2026-08-24 01:32 639231315132253837
65 ms 116.203.140.122
3 2026-08-24 01:15 639231305014280808
34 ms 116.203.140.122
2 2026-08-24 00:23 639231273779380675
38 ms 116.203.140.122
1 2026-08-24 00:07 639231264180839154
40 ms 116.203.140.122