DNS response history for ns.kc-uppertech.com

ns.kc-uppertech.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-27. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 992 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.kc-uppertech.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

992 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.56.80.91

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 ns.kc-uppertech.com

Showing DNS history for 2026-08-27 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-27 10:44 639234233269654413
3 ms 61.56.80.91
33 2026-08-27 10:26 639234222943951923
845 ms 61.56.80.91
32 2026-08-27 10:09 639234212558002823
517 ms 61.56.80.91
31 2026-08-27 09:52 639234202117531850
1690 ms 61.56.80.91
30 2026-08-27 09:34 639234191649612722
3 ms 61.56.80.91
29 2026-08-27 09:17 639234181105879568
1692 ms 61.56.80.91
28 2026-08-27 08:59 639234170713214496
1099 ms 61.56.80.91
27 2026-08-27 08:42 639234160341037652
1107 ms 61.56.80.91
26 2026-08-27 08:25 639234149799404224
1158 ms 61.56.80.91
25 2026-08-27 08:07 639234139553286469
1679 ms 61.56.80.91
24 2026-08-27 07:14 639234107183588293
1128 ms 61.56.80.91
23 2026-08-27 06:56 639234096905435724
1699 ms 61.56.80.91
22 2026-08-27 06:39 639234086579410775
1139 ms 61.56.80.91
21 2026-08-27 06:22 639234076291157956
4 ms 61.56.80.91
20 2026-08-27 06:05 639234065981939454
1691 ms 61.56.80.91
19 2026-08-27 05:48 639234055548642997
1113 ms 61.56.80.91
18 2026-08-27 05:30 639234045267979603
1688 ms 61.56.80.91
17 2026-08-27 05:13 639234034999717463
3 ms 61.56.80.91
16 2026-08-27 04:56 639234024739225358
536 ms 61.56.80.91
15 2026-08-27 04:39 639234014311170162
1109 ms 61.56.80.91
14 2026-08-27 04:21 639234003806017640
1119 ms 61.56.80.91
13 2026-08-27 04:04 639233993356203030
519 ms 61.56.80.91
12 2026-08-27 03:11 639233961301716608
1091 ms 61.56.80.91
11 2026-08-27 02:53 639233950834200647
515 ms 61.56.80.91
10 2026-08-27 02:36 639233940431849026
541 ms 61.56.80.91
9 2026-08-27 02:18 639233930110596398
1106 ms 61.56.80.91
8 2026-08-27 02:01 639233919705434540
3 ms 61.56.80.91
7 2026-08-27 01:44 639233909452807845
1112 ms 61.56.80.91
6 2026-08-27 01:27 639233899096420820
1689 ms 61.56.80.91
5 2026-08-27 01:10 639233888707824939
1110 ms 61.56.80.91
4 2026-08-27 00:52 639233878461203802
1684 ms 61.56.80.91
3 2026-08-27 00:35 639233868060868209
1702 ms 61.56.80.91
2 2026-08-27 00:18 639233857450922991
525 ms 61.56.80.91
1 2026-08-27 00:00 639233846871926285
1103 ms 61.56.80.91