DNS response history for ns1.optimisedhealthwellness.com

ns1.optimisedhealthwellness.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 30 DNS check records, 29 successful responses, 1 failed responses, and 431 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.optimisedhealthwellness.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

431 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

107.152.39.105

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.optimisedhealthwellness.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
30 2026-08-25 10:15 639232492740373468
-
29 2026-08-25 09:58 639232482235303141
124 ms 107.152.39.105
28 2026-08-25 09:40 639232471861770303
153 ms 107.152.39.105
27 2026-08-25 09:23 639232461630217327
158 ms 107.152.39.105
26 2026-08-25 09:06 639232451282965990
125 ms 107.152.39.105
25 2026-08-25 08:49 639232440814614938
150 ms 107.152.39.105
24 2026-08-25 08:31 639232430410720425
11 ms 107.152.39.105
23 2026-08-25 08:14 639232420003096185
2007 ms 107.152.39.105
22 2026-08-25 07:57 639232409467287444
2149 ms 107.152.39.105
21 2026-08-25 07:39 639232399077195997
299 ms 107.152.39.105
20 2026-08-25 07:22 639232388731528337
299 ms 107.152.39.105
19 2026-08-25 07:04 639232378288598612
290 ms 107.152.39.105
18 2026-08-25 06:11 639232346196373643
159 ms 107.152.39.105
17 2026-08-25 05:54 639232336112370741
42 ms 107.152.39.105
16 2026-08-25 05:37 639232326146508970
12 ms 107.152.39.105
15 2026-08-25 05:21 639232316189381720
13 ms 107.152.39.105
14 2026-08-25 05:04 639232306217998913
20 ms 107.152.39.105
13 2026-08-25 04:48 639232296255744174
306 ms 107.152.39.105
12 2026-08-25 04:31 639232286095760789
290 ms 107.152.39.105
11 2026-08-25 04:14 639232276086186273
284 ms 107.152.39.105
10 2026-08-25 03:57 639232265900986425
159 ms 107.152.39.105
9 2026-08-25 03:40 639232255723518075
125 ms 107.152.39.105
8 2026-08-25 03:23 639232245484452890
2013 ms 107.152.39.105
7 2026-08-25 03:06 639232235157175331
2122 ms 107.152.39.105
6 2026-08-25 02:13 639232203197189095
225 ms 107.152.39.105
5 2026-08-25 01:55 639232192844564298
125 ms 107.152.39.105
4 2026-08-25 01:38 639232182496008942
139 ms 107.152.39.105
3 2026-08-25 01:21 639232172197053132
289 ms 107.152.39.105
2 2026-08-25 00:28 639232140250307418
295 ms 107.152.39.105
1 2026-08-25 00:11 639232129927860324
113 ms 107.152.39.105