DNS response history for ns1.kc-rail.link

ns1.kc-rail.link 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 34 DNS check records, 34 successful responses, 0 failed responses, and 400 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.kc-rail.link.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

400 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

15.197.177.102

Most recently resolved hosting IP on selected date

Successful Responses

34

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.kc-rail.link

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
34 2026-08-24 14:03 639231765923559455
3 ms 15.197.177.102
33 2026-08-24 13:46 639231755868832964
4 ms 15.197.177.102
32 2026-08-24 13:29 639231745628278877
19 ms 15.197.177.102
31 2026-08-24 13:12 639231735407682062
54 ms 15.197.177.102
30 2026-08-24 12:19 639231703815441688
4 ms 15.197.177.102
29 2026-08-24 12:03 639231693747052549
47 ms 15.197.177.102
28 2026-08-24 11:46 639231683712487276
42 ms 15.197.177.102
27 2026-08-24 11:29 639231673513573868
39 ms 15.197.177.102
26 2026-08-24 10:36 639231641791249939
31 ms 15.197.177.102
25 2026-08-24 10:19 639231631866211033
2019 ms 15.197.177.102
24 2026-08-24 10:02 639231621644955316
44 ms 15.197.177.102
23 2026-08-24 09:45 639231611478799259
41 ms 15.197.177.102
22 2026-08-24 08:53 639231579923718211
2221 ms 15.197.177.102
21 2026-08-24 08:36 639231569810702936
194 ms 15.197.177.102
20 2026-08-24 08:19 639231559762411619
30 ms 15.197.177.102
19 2026-08-24 08:02 639231549663595407
17 ms 15.197.177.102
18 2026-08-24 07:10 639231518076817246
83 ms 15.197.177.102
17 2026-08-24 06:53 639231508078650885
2019 ms 15.197.177.102
16 2026-08-24 06:37 639231498210697093
2021 ms 15.197.177.102
15 2026-08-24 06:20 639231488109699360
32 ms 15.197.177.102
14 2026-08-24 05:28 639231456772510692
19 ms 15.197.177.102
13 2026-08-24 05:12 639231447084631185
39 ms 15.197.177.102
12 2026-08-24 04:55 639231437208519473
18 ms 15.197.177.102
11 2026-08-24 04:38 639231427209627490
31 ms 15.197.177.102
10 2026-08-24 03:46 639231395791246644
16 ms 15.197.177.102
9 2026-08-24 03:30 639231386075551458
40 ms 15.197.177.102
8 2026-08-24 03:13 639231376208713791
41 ms 15.197.177.102
7 2026-08-24 02:57 639231366170589276
14 ms 15.197.177.102
6 2026-08-24 02:04 639231334732159368
42 ms 15.197.177.102
5 2026-08-24 01:48 639231325035670078
34 ms 15.197.177.102
4 2026-08-24 01:31 639231315132253837
2085 ms 15.197.177.102
3 2026-08-24 01:15 639231305014280808
29 ms 15.197.177.102
2 2026-08-24 00:23 639231273779380675
211 ms 15.197.177.102
1 2026-08-24 00:07 639231264180839154
2033 ms 15.197.177.102