DNS response history for ns1.optimalwellnesspath.info

ns1.optimalwellnesspath.info 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 32 DNS check records, 32 successful responses, 0 failed responses, and 206 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 ns1.optimalwellnesspath.info.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

206 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.129.87.28

Most recently resolved hosting IP on selected date

Successful Responses

32

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 ns1.optimalwellnesspath.info

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
32 2026-08-25 11:30 639232535349285207
163 ms 45.129.87.28
31 2026-08-25 11:13 639232524938080723
154 ms 45.129.87.28
30 2026-08-25 10:19 639232492740373468
5 ms 45.129.87.28
29 2026-08-25 10:02 639232482235303141
4 ms 45.129.87.28
28 2026-08-25 09:44 639232471861770303
159 ms 45.129.87.28
27 2026-08-25 09:27 639232461630217327
6 ms 45.129.87.28
26 2026-08-25 09:10 639232451282965990
695 ms 45.129.87.28
25 2026-08-25 08:52 639232440814614938
270 ms 45.129.87.28
24 2026-08-25 08:35 639232430410720425
3 ms 45.129.87.28
23 2026-08-25 08:18 639232420003096185
305 ms 45.129.87.28
22 2026-08-25 08:00 639232409467287444
184 ms 45.129.87.28
21 2026-08-25 07:43 639232399077195997
5 ms 45.129.87.28
20 2026-08-25 07:26 639232388731528337
411 ms 45.129.87.28
19 2026-08-25 07:08 639232378288598612
148 ms 45.129.87.28
18 2026-08-25 06:15 639232346196373643
4 ms 45.129.87.28
17 2026-08-25 05:58 639232336112370741
518 ms 45.129.87.28
16 2026-08-25 05:41 639232326146508970
572 ms 45.129.87.28
15 2026-08-25 05:24 639232316189381720
159 ms 45.129.87.28
14 2026-08-25 05:08 639232306217998913
3 ms 45.129.87.28
13 2026-08-25 04:51 639232296255744174
324 ms 45.129.87.28
12 2026-08-25 04:34 639232286095760789
335 ms 45.129.87.28
11 2026-08-25 04:17 639232276086186273
7 ms 45.129.87.28
10 2026-08-25 04:01 639232265900986425
152 ms 45.129.87.28
9 2026-08-25 03:44 639232255723518075
316 ms 45.129.87.28
8 2026-08-25 03:27 639232245484452890
194 ms 45.129.87.28
7 2026-08-25 03:10 639232235157175331
339 ms 45.129.87.28
6 2026-08-25 02:16 639232203197189095
323 ms 45.129.87.28
5 2026-08-25 01:59 639232192844564298
337 ms 45.129.87.28
4 2026-08-25 01:42 639232182496008942
177 ms 45.129.87.28
3 2026-08-25 01:25 639232172197053132
152 ms 45.129.87.28
2 2026-08-25 00:31 639232140250307418
176 ms 45.129.87.28
1 2026-08-25 00:14 639232129927860324
4 ms 45.129.87.28