DNS response history for ns2.tecture.com

ns2.tecture.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 232 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.tecture.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

232 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

52.26.149.104

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 ns2.tecture.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:24 639234296664302575
104 ms 52.26.149.104
36 2026-08-27 12:07 639234286253196126
206 ms 52.26.149.104
35 2026-08-27 11:13 639234253963286387
177 ms 52.26.149.104
34 2026-08-27 10:56 639234243654907465
100 ms 52.26.149.104
33 2026-08-27 10:38 639234233269654413
104 ms 52.26.149.104
32 2026-08-27 10:21 639234222943951923
203 ms 52.26.149.104
31 2026-08-27 10:04 639234212558002823
102 ms 52.26.149.104
30 2026-08-27 09:47 639234202117531850
214 ms 52.26.149.104
29 2026-08-27 09:29 639234191649612722
99 ms 52.26.149.104
28 2026-08-27 09:12 639234181105879568
224 ms 52.26.149.104
27 2026-08-27 08:54 639234170713214496
204 ms 52.26.149.104
26 2026-08-27 08:37 639234160341037652
97 ms 52.26.149.104
25 2026-08-27 08:19 639234149799404224
202 ms 52.26.149.104
24 2026-08-27 08:02 639234139553286469
200 ms 52.26.149.104
23 2026-08-27 07:08 639234107183588293
104 ms 52.26.149.104
22 2026-08-27 06:51 639234096905435724
213 ms 52.26.149.104
21 2026-08-27 06:34 639234086579410775
202 ms 52.26.149.104
20 2026-08-27 06:17 639234076291157956
206 ms 52.26.149.104
19 2026-08-27 06:00 639234065981939454
216 ms 52.26.149.104
18 2026-08-27 05:43 639234055548642997
328 ms 52.26.149.104
17 2026-08-27 05:25 639234045267979603
101 ms 52.26.149.104
16 2026-08-27 05:08 639234034999717463
103 ms 52.26.149.104
15 2026-08-27 04:51 639234024739225358
229 ms 52.26.149.104
14 2026-08-27 04:34 639234014311170162
101 ms 52.26.149.104
13 2026-08-27 04:16 639234003806017640
331 ms 52.26.149.104
12 2026-08-27 03:59 639233993356203030
102 ms 52.26.149.104
11 2026-08-27 03:05 639233961301716608
274 ms 52.26.149.104
10 2026-08-27 02:48 639233950834200647
168 ms 52.26.149.104
9 2026-08-27 02:31 639233940431849026
114 ms 52.26.149.104
8 2026-08-27 02:13 639233930110596398
213 ms 52.26.149.104
7 2026-08-27 01:56 639233919705434540
2178 ms 52.26.149.104
6 2026-08-27 01:39 639233909452807845
134 ms 52.26.149.104
5 2026-08-27 01:22 639233899096420820
270 ms 52.26.149.104
4 2026-08-27 01:04 639233888707824939
201 ms 52.26.149.104
3 2026-08-27 00:47 639233878461203802
197 ms 52.26.149.104
2 2026-08-27 00:30 639233868060868209
200 ms 52.26.149.104
1 2026-08-27 00:12 639233857450922991
170 ms 52.26.149.104