DNS response history for ns.city-link.info

ns.city-link.info 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 187 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.city-link.info.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

187 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

194.50.128.6

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.city-link.info

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:10 639231765923559455
4066 ms 194.50.128.6
33 2026-08-24 13:53 639231755868832964
124 ms 194.50.128.6
32 2026-08-24 13:36 639231745628278877
208 ms 194.50.128.6
31 2026-08-24 13:19 639231735407682062
112 ms 194.50.128.6
30 2026-08-24 12:26 639231703815441688
63 ms 194.50.128.6
29 2026-08-24 12:10 639231693747052549
118 ms 194.50.128.6
28 2026-08-24 11:53 639231683712487276
8 ms 194.50.128.6
27 2026-08-24 11:36 639231673513573868
6 ms 194.50.128.6
26 2026-08-24 10:43 639231641791249939
51 ms 194.50.128.6
25 2026-08-24 10:26 639231631866211033
114 ms 194.50.128.6
24 2026-08-24 10:09 639231621644955316
235 ms 194.50.128.6
23 2026-08-24 09:52 639231611478799259
106 ms 194.50.128.6
22 2026-08-24 09:00 639231579923718211
134 ms 194.50.128.6
21 2026-08-24 08:43 639231569810702936
33 ms 194.50.128.6
20 2026-08-24 08:26 639231559762411619
10 ms 194.50.128.6
19 2026-08-24 08:09 639231549663595407
71 ms 194.50.128.6
18 2026-08-24 07:16 639231518076817246
5 ms 194.50.128.6
17 2026-08-24 07:00 639231508078650885
23 ms 194.50.128.6
16 2026-08-24 06:43 639231498210697093
220 ms 194.50.128.6
15 2026-08-24 06:27 639231488109699360
8 ms 194.50.128.6
14 2026-08-24 05:34 639231456772510692
139 ms 194.50.128.6
13 2026-08-24 05:18 639231447084631185
118 ms 194.50.128.6
12 2026-08-24 05:02 639231437208519473
4 ms 194.50.128.6
11 2026-08-24 04:45 639231427209627490
3 ms 194.50.128.6
10 2026-08-24 03:52 639231395791246644
6 ms 194.50.128.6
9 2026-08-24 03:36 639231386075551458
2 ms 194.50.128.6
8 2026-08-24 03:20 639231376208713791
206 ms 194.50.128.6
7 2026-08-24 03:04 639231366170589276
22 ms 194.50.128.6
6 2026-08-24 02:11 639231334732159368
121 ms 194.50.128.6
5 2026-08-24 01:55 639231325035670078
5 ms 194.50.128.6
4 2026-08-24 01:38 639231315132253837
4 ms 194.50.128.6
3 2026-08-24 01:22 639231305014280808
3 ms 194.50.128.6
2 2026-08-24 00:29 639231273779380675
10 ms 194.50.128.6
1 2026-08-24 00:13 639231264180839154
3 ms 194.50.128.6