DNS response history for ns2.automatewp.com

ns2.automatewp.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-25. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 278 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.automatewp.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

278 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

165.140.70.173

Most recently resolved hosting IP on selected date

Successful Responses

36

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.automatewp.com

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
36 2026-08-25 12:36 639232576780683689
322 ms 165.140.70.173
35 2026-08-25 12:18 639232566381512620
259 ms 165.140.70.173
34 2026-08-25 12:01 639232556111768563
295 ms 165.140.70.173
33 2026-08-25 11:44 639232545839529039
265 ms 165.140.70.173
32 2026-08-25 11:26 639232535349285207
285 ms 165.140.70.173
31 2026-08-25 11:09 639232524938080723
573 ms 165.140.70.173
30 2026-08-25 10:15 639232492740373468
142 ms 165.140.70.173
29 2026-08-25 09:58 639232482235303141
310 ms 165.140.70.173
28 2026-08-25 09:40 639232471861770303
299 ms 165.140.70.173
27 2026-08-25 09:23 639232461630217327
314 ms 165.140.70.173
26 2026-08-25 09:06 639232451282965990
461 ms 165.140.70.173
25 2026-08-25 08:49 639232440814614938
306 ms 165.140.70.173
24 2026-08-25 08:31 639232430410720425
562 ms 165.140.70.173
23 2026-08-25 08:14 639232420003096185
292 ms 165.140.70.173
22 2026-08-25 07:57 639232409467287444
239 ms 165.140.70.173
21 2026-08-25 07:39 639232399077195997
269 ms 165.140.70.173
20 2026-08-25 07:22 639232388731528337
299 ms 165.140.70.173
19 2026-08-25 07:05 639232378288598612
253 ms 165.140.70.173
18 2026-08-25 06:11 639232346196373643
267 ms 165.140.70.173
17 2026-08-25 05:54 639232336112370741
129 ms 165.140.70.173
16 2026-08-25 05:38 639232326146508970
17 ms 165.140.70.173
15 2026-08-25 05:21 639232316189381720
252 ms 165.140.70.173
14 2026-08-25 05:05 639232306217998913
265 ms 165.140.70.173
13 2026-08-25 04:48 639232296255744174
365 ms 165.140.70.173
12 2026-08-25 04:31 639232286095760789
340 ms 165.140.70.173
11 2026-08-25 04:14 639232276086186273
5 ms 165.140.70.173
10 2026-08-25 03:57 639232265900986425
303 ms 165.140.70.173
9 2026-08-25 03:40 639232255723518075
10 ms 165.140.70.173
8 2026-08-25 03:23 639232245484452890
272 ms 165.140.70.173
7 2026-08-25 03:06 639232235157175331
317 ms 165.140.70.173
6 2026-08-25 02:13 639232203197189095
274 ms 165.140.70.173
5 2026-08-25 01:56 639232192844564298
315 ms 165.140.70.173
4 2026-08-25 01:38 639232182496008942
300 ms 165.140.70.173
3 2026-08-25 01:21 639232172197053132
263 ms 165.140.70.173
2 2026-08-25 00:28 639232140250307418
293 ms 165.140.70.173
1 2026-08-25 00:11 639232129927860324
284 ms 165.140.70.173