DNS response history for ns2.intechold.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

222 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.71.16.121

Most recently resolved hosting IP on selected date

Successful Responses

35

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.intechold.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
35 2026-08-27 11:10 639234253963286387
83 ms 45.71.16.121
34 2026-08-27 10:53 639234243654907465
49 ms 45.71.16.121
33 2026-08-27 10:36 639234233269654413
113 ms 45.71.16.121
32 2026-08-27 10:19 639234222943951923
81 ms 45.71.16.121
31 2026-08-27 10:01 639234212558002823
58 ms 45.71.16.121
30 2026-08-27 09:44 639234202117531850
206 ms 45.71.16.121
29 2026-08-27 09:26 639234191649612722
76 ms 45.71.16.121
28 2026-08-27 09:09 639234181105879568
2043 ms 45.71.16.121
27 2026-08-27 08:52 639234170713214496
61 ms 45.71.16.121
26 2026-08-27 08:34 639234160341037652
71 ms 45.71.16.121
25 2026-08-27 08:17 639234149799404224
40 ms 45.71.16.121
24 2026-08-27 08:00 639234139553286469
64 ms 45.71.16.121
23 2026-08-27 07:06 639234107183588293
47 ms 45.71.16.121
22 2026-08-27 06:49 639234096905435724
93 ms 45.71.16.121
21 2026-08-27 06:31 639234086579410775
59 ms 45.71.16.121
20 2026-08-27 06:14 639234076291157956
86 ms 45.71.16.121
19 2026-08-27 05:57 639234065981939454
82 ms 45.71.16.121
18 2026-08-27 05:40 639234055548642997
190 ms 45.71.16.121
17 2026-08-27 05:22 639234045267979603
84 ms 45.71.16.121
16 2026-08-27 05:06 639234034999717463
193 ms 45.71.16.121
15 2026-08-27 04:48 639234024739225358
46 ms 45.71.16.121
14 2026-08-27 04:31 639234014311170162
37 ms 45.71.16.121
13 2026-08-27 04:14 639234003806017640
74 ms 45.71.16.121
12 2026-08-27 03:56 639233993356203030
170 ms 45.71.16.121
11 2026-08-27 03:03 639233961301716608
79 ms 45.71.16.121
10 2026-08-27 02:45 639233950834200647
94 ms 45.71.16.121
9 2026-08-27 02:28 639233940431849026
69 ms 45.71.16.121
8 2026-08-27 02:11 639233930110596398
100 ms 45.71.16.121
7 2026-08-27 01:54 639233919705434540
92 ms 45.71.16.121
6 2026-08-27 01:36 639233909452807845
184 ms 45.71.16.121
5 2026-08-27 01:19 639233899096420820
113 ms 45.71.16.121
4 2026-08-27 01:02 639233888707824939
97 ms 45.71.16.121
3 2026-08-27 00:45 639233878461203802
160 ms 45.71.16.121
2 2026-08-27 00:27 639233868060868209
233 ms 45.71.16.121
1 2026-08-27 00:10 639233857450922991
2439 ms 45.71.16.121