DNS response history for ns2.wearabletechwatch.net

ns2.wearabletechwatch.net 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-25. For this date, NameServerHistory found 34 DNS check records, 32 successful responses, 2 failed responses, and 258 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.wearabletechwatch.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

258 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

54.39.173.140

Most recently resolved hosting IP on selected date

Successful Responses

32

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

6%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.wearabletechwatch.net

Showing DNS history for 2026-08-25 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-25 12:05 639232556111768563
220 ms 54.39.173.140
33 2026-08-25 11:48 639232545839529039
224 ms 54.39.173.140
32 2026-08-25 11:30 639232535349285207
230 ms 54.39.173.140
31 2026-08-25 11:13 639232524938080723
106 ms 54.39.173.140
30 2026-08-25 10:19 639232492740373468
216 ms 54.39.173.140
29 2026-08-25 10:02 639232482235303141
223 ms 54.39.173.140
28 2026-08-25 09:45 639232471861770303
5 ms 54.39.173.140
27 2026-08-25 09:27 639232461630217327
-
26 2026-08-25 09:10 639232451282965990
221 ms 54.39.173.140
25 2026-08-25 08:53 639232440814614938
223 ms 54.39.173.140
24 2026-08-25 08:35 639232430410720425
3 ms 54.39.173.140
23 2026-08-25 08:18 639232420003096185
4 ms 54.39.173.140
22 2026-08-25 08:01 639232409467287444
217 ms 54.39.173.140
21 2026-08-25 07:43 639232399077195997
5 ms 54.39.173.140
20 2026-08-25 07:26 639232388731528337
219 ms 54.39.173.140
19 2026-08-25 07:09 639232378288598612
5 ms 54.39.173.140
18 2026-08-25 06:15 639232346196373643
4 ms 54.39.173.140
17 2026-08-25 05:58 639232336112370741
4 ms 54.39.173.140
16 2026-08-25 05:41 639232326146508970
3 ms 54.39.173.140
15 2026-08-25 05:25 639232316189381720
2 ms 54.39.173.140
14 2026-08-25 05:08 639232306217998913
2115 ms 54.39.173.140
13 2026-08-25 04:52 639232296255744174
4 ms 54.39.173.140
12 2026-08-25 04:35 639232286095760789
217 ms 54.39.173.140
11 2026-08-25 04:18 639232276086186273
217 ms 54.39.173.140
10 2026-08-25 04:01 639232265900986425
218 ms 54.39.173.140
9 2026-08-25 03:44 639232255723518075
-
8 2026-08-25 03:27 639232245484452890
3 ms 54.39.173.140
7 2026-08-25 03:10 639232235157175331
116 ms 54.39.173.140
6 2026-08-25 02:17 639232203197189095
218 ms 54.39.173.140
5 2026-08-25 02:00 639232192844564298
219 ms 54.39.173.140
4 2026-08-25 01:42 639232182496008942
218 ms 54.39.173.140
3 2026-08-25 01:25 639232172197053132
235 ms 54.39.173.140
2 2026-08-25 00:32 639232140250307418
2101 ms 54.39.173.140
1 2026-08-25 00:15 639232129927860324
228 ms 54.39.173.140