DNS response history for ns2.kritth.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

338 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.91.132.92

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

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
29 2026-08-24 12:08 639231693747052549
432 ms 45.91.132.92
28 2026-08-24 11:51 639231683712487276
413 ms 45.91.132.92
27 2026-08-24 11:34 639231673513573868
428 ms 45.91.132.92
26 2026-08-24 10:41 639231641791249939
193 ms 45.91.132.92
25 2026-08-24 10:25 639231631866211033
413 ms 45.91.132.92
24 2026-08-24 10:08 639231621644955316
432 ms 45.91.132.92
23 2026-08-24 09:51 639231611478799259
364 ms 45.91.132.92
22 2026-08-24 08:58 639231579923718211
425 ms 45.91.132.92
21 2026-08-24 08:41 639231569810702936
12 ms 45.91.132.92
20 2026-08-24 08:24 639231559762411619
411 ms 45.91.132.92
19 2026-08-24 08:08 639231549663595407
397 ms 45.91.132.92
18 2026-08-24 07:15 639231518076817246
421 ms 45.91.132.92
17 2026-08-24 06:59 639231508078650885
419 ms 45.91.132.92
16 2026-08-24 06:42 639231498210697093
3 ms 45.91.132.92
15 2026-08-24 06:25 639231488109699360
9 ms 45.91.132.92
14 2026-08-24 05:33 639231456772510692
340 ms 45.91.132.92
13 2026-08-24 05:17 639231447084631185
428 ms 45.91.132.92
12 2026-08-24 05:00 639231437208519473
429 ms 45.91.132.92
11 2026-08-24 04:43 639231427209627490
3 ms 45.91.132.92
10 2026-08-24 03:51 639231395791246644
3 ms 45.91.132.92
9 2026-08-24 03:35 639231386075551458
441 ms 45.91.132.92
8 2026-08-24 03:19 639231376208713791
193 ms 45.91.132.92
7 2026-08-24 03:02 639231366170589276
386 ms 45.91.132.92
6 2026-08-24 02:10 639231334732159368
2343 ms 45.91.132.92
5 2026-08-24 01:53 639231325035670078
3 ms 45.91.132.92
4 2026-08-24 01:37 639231315132253837
2 ms 45.91.132.92
3 2026-08-24 01:20 639231305014280808
430 ms 45.91.132.92
2 2026-08-24 00:28 639231273779380675
15 ms 45.91.132.92
1 2026-08-24 00:12 639231264180839154
4 ms 45.91.132.92