DNS response history for ve9.curehealthconnect.com

ve9.curehealthconnect.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 35 DNS check records, 35 successful responses, 0 failed responses, and 612 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 ve9.curehealthconnect.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

612 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

163.61.103.134

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ve9.curehealthconnect.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
35 2026-08-25 12:22 639232566381512620
5 ms 163.61.103.134
34 2026-08-25 12:05 639232556111768563
2258 ms 163.61.103.134
33 2026-08-25 11:48 639232545839529039
170 ms 163.61.103.134
32 2026-08-25 11:30 639232535349285207
332 ms 163.61.103.134
31 2026-08-25 11:13 639232524938080723
310 ms 163.61.103.134
30 2026-08-25 10:19 639232492740373468
159 ms 163.61.103.134
29 2026-08-25 10:02 639232482235303141
4248 ms 163.61.103.134
28 2026-08-25 09:44 639232471861770303
331 ms 163.61.103.134
27 2026-08-25 09:27 639232461630217327
325 ms 163.61.103.134
26 2026-08-25 09:10 639232451282965990
160 ms 163.61.103.134
25 2026-08-25 08:53 639232440814614938
319 ms 163.61.103.134
24 2026-08-25 08:35 639232430410720425
320 ms 163.61.103.134
23 2026-08-25 08:18 639232420003096185
9 ms 163.61.103.134
22 2026-08-25 08:01 639232409467287444
273 ms 163.61.103.134
21 2026-08-25 07:43 639232399077195997
319 ms 163.61.103.134
20 2026-08-25 07:26 639232388731528337
2177 ms 163.61.103.134
19 2026-08-25 07:09 639232378288598612
318 ms 163.61.103.134
18 2026-08-25 06:15 639232346196373643
2269 ms 163.61.103.134
17 2026-08-25 05:58 639232336112370741
3 ms 163.61.103.134
16 2026-08-25 05:41 639232326146508970
2242 ms 163.61.103.134
15 2026-08-25 05:25 639232316189381720
4 ms 163.61.103.134
14 2026-08-25 05:08 639232306217998913
32 ms 163.61.103.134
13 2026-08-25 04:52 639232296255744174
318 ms 163.61.103.134
12 2026-08-25 04:35 639232286095760789
315 ms 163.61.103.134
11 2026-08-25 04:18 639232276086186273
316 ms 163.61.103.134
10 2026-08-25 04:01 639232265900986425
3 ms 163.61.103.134
9 2026-08-25 03:44 639232255723518075
227 ms 163.61.103.134
8 2026-08-25 03:27 639232245484452890
3 ms 163.61.103.134
7 2026-08-25 03:10 639232235157175331
3 ms 163.61.103.134
6 2026-08-25 02:17 639232203197189095
282 ms 163.61.103.134
5 2026-08-25 02:00 639232192844564298
2244 ms 163.61.103.134
4 2026-08-25 01:42 639232182496008942
317 ms 163.61.103.134
3 2026-08-25 01:25 639232172197053132
319 ms 163.61.103.134
2 2026-08-25 00:32 639232140250307418
321 ms 163.61.103.134
1 2026-08-25 00:15 639232129927860324
160 ms 163.61.103.134