DNS response history for ns.kirishi.net

ns.kirishi.net 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-26. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 88 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 ns.kirishi.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

88 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

79.173.127.206

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns.kirishi.net

Showing DNS history for 2026-08-26 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
36 2026-08-26 12:09 639233424567558554
97 ms 79.173.127.206
35 2026-08-26 11:51 639233414056832719
59 ms 79.173.127.206
34 2026-08-26 11:34 639233403515141099
102 ms 79.173.127.206
33 2026-08-26 10:39 639233370841350248
54 ms 79.173.127.206
32 2026-08-26 10:22 639233360361507238
68 ms 79.173.127.206
31 2026-08-26 10:04 639233350067824371
107 ms 79.173.127.206
30 2026-08-26 09:47 639233339545274518
97 ms 79.173.127.206
29 2026-08-26 09:30 639233329214918079
100 ms 79.173.127.206
28 2026-08-26 09:12 639233318749762337
67 ms 79.173.127.206
27 2026-08-26 08:55 639233308387917838
97 ms 79.173.127.206
26 2026-08-26 08:38 639233297961740122
99 ms 79.173.127.206
25 2026-08-26 08:20 639233287487159094
105 ms 79.173.127.206
24 2026-08-26 08:03 639233276995531707
34 ms 79.173.127.206
23 2026-08-26 07:45 639233266521568229
109 ms 79.173.127.206
22 2026-08-26 07:28 639233256081047431
101 ms 79.173.127.206
21 2026-08-26 06:34 639233223620132921
62 ms 79.173.127.206
20 2026-08-26 06:17 639233213287814244
149 ms 79.173.127.206
19 2026-08-26 05:59 639233202925983161
25 ms 79.173.127.206
18 2026-08-26 05:42 639233192644780696
99 ms 79.173.127.206
17 2026-08-26 05:25 639233182401183833
111 ms 79.173.127.206
16 2026-08-26 05:08 639233172074181051
96 ms 79.173.127.206
15 2026-08-26 04:51 639233161808421455
8 ms 79.173.127.206
14 2026-08-26 04:33 639233151357344052
97 ms 79.173.127.206
13 2026-08-26 04:16 639233141034116946
147 ms 79.173.127.206
12 2026-08-26 03:59 639233130828334142
92 ms 79.173.127.206
11 2026-08-26 03:42 639233120373450007
100 ms 79.173.127.206
10 2026-08-26 03:24 639233110066216193
99 ms 79.173.127.206
9 2026-08-26 02:31 639233078065410564
95 ms 79.173.127.206
8 2026-08-26 02:14 639233067787457832
59 ms 79.173.127.206
7 2026-08-26 01:57 639233057501801162
55 ms 79.173.127.206
6 2026-08-26 01:40 639233047089431703
110 ms 79.173.127.206
5 2026-08-26 01:22 639233036754790688
100 ms 79.173.127.206
4 2026-08-26 01:05 639233026412602472
100 ms 79.173.127.206
3 2026-08-26 00:48 639233016064066127
98 ms 79.173.127.206
2 2026-08-26 00:31 639233005922655772
96 ms 79.173.127.206
1 2026-08-26 00:14 639232995672256907
56 ms 79.173.127.206