DNS response history for ns1.foo.kim

ns1.foo.kim 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-25. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 389 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 ns1.foo.kim.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

389 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

166.70.220.103

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 ns1.foo.kim

Showing DNS history for 2026-08-25 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-25 12:39 639232576780683689
322 ms 166.70.220.103
35 2026-08-25 12:21 639232566381512620
2030 ms 166.70.220.103
34 2026-08-25 12:04 639232556111768563
155 ms 166.70.220.103
33 2026-08-25 11:47 639232545839529039
168 ms 166.70.220.103
32 2026-08-25 11:30 639232535349285207
166 ms 166.70.220.103
31 2026-08-25 11:12 639232524938080723
163 ms 166.70.220.103
30 2026-08-25 10:19 639232492740373468
323 ms 166.70.220.103
29 2026-08-25 10:01 639232482235303141
332 ms 166.70.220.103
28 2026-08-25 09:44 639232471861770303
189 ms 166.70.220.103
27 2026-08-25 09:27 639232461630217327
9 ms 166.70.220.103
26 2026-08-25 09:10 639232451282965990
187 ms 166.70.220.103
25 2026-08-25 08:52 639232440814614938
315 ms 166.70.220.103
24 2026-08-25 08:35 639232430410720425
320 ms 166.70.220.103
23 2026-08-25 08:18 639232420003096185
338 ms 166.70.220.103
22 2026-08-25 08:00 639232409467287444
330 ms 166.70.220.103
21 2026-08-25 07:43 639232399077195997
2302 ms 166.70.220.103
20 2026-08-25 07:25 639232388731528337
440 ms 166.70.220.103
19 2026-08-25 07:08 639232378288598612
316 ms 166.70.220.103
18 2026-08-25 06:14 639232346196373643
3 ms 166.70.220.103
17 2026-08-25 05:57 639232336112370741
164 ms 166.70.220.103
16 2026-08-25 05:41 639232326146508970
337 ms 166.70.220.103
15 2026-08-25 05:24 639232316189381720
163 ms 166.70.220.103
14 2026-08-25 05:08 639232306217998913
457 ms 166.70.220.103
13 2026-08-25 04:51 639232296255744174
2219 ms 166.70.220.103
12 2026-08-25 04:34 639232286095760789
481 ms 166.70.220.103
11 2026-08-25 04:17 639232276086186273
3 ms 166.70.220.103
10 2026-08-25 04:01 639232265900986425
4 ms 166.70.220.103
9 2026-08-25 03:44 639232255723518075
2 ms 166.70.220.103
8 2026-08-25 03:27 639232245484452890
2 ms 166.70.220.103
7 2026-08-25 03:09 639232235157175331
343 ms 166.70.220.103
6 2026-08-25 02:16 639232203197189095
2 ms 166.70.220.103
5 2026-08-25 01:59 639232192844564298
320 ms 166.70.220.103
4 2026-08-25 01:42 639232182496008942
318 ms 166.70.220.103
3 2026-08-25 01:24 639232172197053132
440 ms 166.70.220.103
2 2026-08-25 00:31 639232140250307418
3 ms 166.70.220.103
1 2026-08-25 00:14 639232129927860324
330 ms 166.70.220.103