DNS response history for ns2.interlinkcomputing.com

ns2.interlinkcomputing.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 29 DNS check records, 29 successful responses, 0 failed responses, and 2578 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 ns2.interlinkcomputing.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

2578 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.225.163.52

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns2.interlinkcomputing.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
29 2026-08-27 09:18 639234181105879568
2008 ms 67.225.163.52
28 2026-08-27 09:00 639234170713214496
3548 ms 67.225.163.52
27 2026-08-27 08:43 639234160341037652
3512 ms 67.225.163.52
26 2026-08-27 08:26 639234149799404224
2024 ms 67.225.163.52
25 2026-08-27 08:08 639234139553286469
2035 ms 67.225.163.52
24 2026-08-27 07:14 639234107183588293
3512 ms 67.225.163.52
23 2026-08-27 06:57 639234096905435724
2008 ms 67.225.163.52
22 2026-08-27 06:40 639234086579410775
2030 ms 67.225.163.52
21 2026-08-27 06:23 639234076291157956
2013 ms 67.225.163.52
20 2026-08-27 06:06 639234065981939454
2007 ms 67.225.163.52
19 2026-08-27 05:48 639234055548642997
2032 ms 67.225.163.52
18 2026-08-27 05:31 639234045267979603
2031 ms 67.225.163.52
17 2026-08-27 05:14 639234034999717463
2009 ms 67.225.163.52
16 2026-08-27 04:57 639234024739225358
2008 ms 67.225.163.52
15 2026-08-27 04:40 639234014311170162
3537 ms 67.225.163.52
14 2026-08-27 04:22 639234003806017640
3516 ms 67.225.163.52
13 2026-08-27 04:05 639233993356203030
2012 ms 67.225.163.52
12 2026-08-27 03:11 639233961301716608
4020 ms 67.225.163.52
11 2026-08-27 02:54 639233950834200647
2007 ms 67.225.163.52
10 2026-08-27 02:36 639233940431849026
3511 ms 67.225.163.52
9 2026-08-27 02:19 639233930110596398
2008 ms 67.225.163.52
8 2026-08-27 02:02 639233919705434540
2008 ms 67.225.163.52
7 2026-08-27 01:45 639233909452807845
3512 ms 67.225.163.52
6 2026-08-27 01:27 639233899096420820
2093 ms 67.225.163.52
5 2026-08-27 01:10 639233888707824939
3512 ms 67.225.163.52
4 2026-08-27 00:53 639233878461203802
2032 ms 67.225.163.52
3 2026-08-27 00:36 639233868060868209
4014 ms 67.225.163.52
2 2026-08-27 00:18 639233857450922991
2164 ms 67.225.163.52
1 2026-08-27 00:01 639233846871926285
2037 ms 67.225.163.52