DNS response history for ns1.linkedns.com

ns1.linkedns.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 37 DNS check records, 37 successful responses, 0 failed responses, and 329 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.linkedns.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

329 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.68.189.56

Most recently resolved hosting IP on selected date

Successful Responses

37

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.linkedns.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
37 2026-08-27 12:18 639234296664302575
180 ms 51.68.189.56
36 2026-08-27 12:01 639234286253196126
38 ms 51.68.189.56
35 2026-08-27 11:07 639234253963286387
2181 ms 51.68.189.56
34 2026-08-27 10:50 639234243654907465
22 ms 51.68.189.56
33 2026-08-27 10:33 639234233269654413
242 ms 51.68.189.56
32 2026-08-27 10:15 639234222943951923
63 ms 51.68.189.56
31 2026-08-27 09:58 639234212558002823
25 ms 51.68.189.56
30 2026-08-27 09:41 639234202117531850
41 ms 51.68.189.56
29 2026-08-27 09:23 639234191649612722
2017 ms 51.68.189.56
28 2026-08-27 09:06 639234181105879568
33 ms 51.68.189.56
27 2026-08-27 08:48 639234170713214496
2041 ms 51.68.189.56
26 2026-08-27 08:31 639234160341037652
50 ms 51.68.189.56
25 2026-08-27 08:14 639234149799404224
32 ms 51.68.189.56
24 2026-08-27 07:56 639234139553286469
31 ms 51.68.189.56
23 2026-08-27 07:02 639234107183588293
27 ms 51.68.189.56
22 2026-08-27 06:45 639234096905435724
51 ms 51.68.189.56
21 2026-08-27 06:28 639234086579410775
24 ms 51.68.189.56
20 2026-08-27 06:11 639234076291157956
14 ms 51.68.189.56
19 2026-08-27 05:54 639234065981939454
32 ms 51.68.189.56
18 2026-08-27 05:37 639234055548642997
2021 ms 51.68.189.56
17 2026-08-27 05:19 639234045267979603
31 ms 51.68.189.56
16 2026-08-27 05:02 639234034999717463
171 ms 51.68.189.56
15 2026-08-27 04:45 639234024739225358
30 ms 51.68.189.56
14 2026-08-27 04:28 639234014311170162
33 ms 51.68.189.56
13 2026-08-27 04:10 639234003806017640
36 ms 51.68.189.56
12 2026-08-27 03:53 639233993356203030
23 ms 51.68.189.56
11 2026-08-27 02:59 639233961301716608
63 ms 51.68.189.56
10 2026-08-27 02:42 639233950834200647
2012 ms 51.68.189.56
9 2026-08-27 02:25 639233940431849026
186 ms 51.68.189.56
8 2026-08-27 02:07 639233930110596398
23 ms 51.68.189.56
7 2026-08-27 01:50 639233919705434540
31 ms 51.68.189.56
6 2026-08-27 01:33 639233909452807845
185 ms 51.68.189.56
5 2026-08-27 01:16 639233899096420820
34 ms 51.68.189.56
4 2026-08-27 00:58 639233888707824939
28 ms 51.68.189.56
3 2026-08-27 00:41 639233878461203802
27 ms 51.68.189.56
2 2026-08-27 00:24 639233868060868209
53 ms 51.68.189.56
1 2026-08-27 00:06 639233857450922991
25 ms 51.68.189.56