DNS response history for ns3.chuladoctorwellness.com

ns3.chuladoctorwellness.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 31 DNS check records, 31 successful responses, 0 failed responses, and 500 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 ns3.chuladoctorwellness.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

500 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

147.50.228.44

Most recently resolved hosting IP on selected date

Successful Responses

31

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 ns3.chuladoctorwellness.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
31 2026-08-25 11:13 639232524938080723
367 ms 147.50.228.44
30 2026-08-25 10:19 639232492740373468
2213 ms 147.50.228.44
29 2026-08-25 10:02 639232482235303141
374 ms 147.50.228.44
28 2026-08-25 09:45 639232471861770303
373 ms 147.50.228.44
27 2026-08-25 09:27 639232461630217327
394 ms 147.50.228.44
26 2026-08-25 09:10 639232451282965990
393 ms 147.50.228.44
25 2026-08-25 08:53 639232440814614938
384 ms 147.50.228.44
24 2026-08-25 08:36 639232430410720425
381 ms 147.50.228.44
23 2026-08-25 08:18 639232420003096185
373 ms 147.50.228.44
22 2026-08-25 08:01 639232409467287444
412 ms 147.50.228.44
21 2026-08-25 07:43 639232399077195997
403 ms 147.50.228.44
20 2026-08-25 07:26 639232388731528337
380 ms 147.50.228.44
19 2026-08-25 07:09 639232378288598612
382 ms 147.50.228.44
18 2026-08-25 06:15 639232346196373643
414 ms 147.50.228.44
17 2026-08-25 05:58 639232336112370741
5 ms 147.50.228.44
16 2026-08-25 05:42 639232326146508970
2 ms 147.50.228.44
15 2026-08-25 05:25 639232316189381720
2233 ms 147.50.228.44
14 2026-08-25 05:08 639232306217998913
4 ms 147.50.228.44
13 2026-08-25 04:52 639232296255744174
4 ms 147.50.228.44
12 2026-08-25 04:35 639232286095760789
390 ms 147.50.228.44
11 2026-08-25 04:18 639232276086186273
372 ms 147.50.228.44
10 2026-08-25 04:01 639232265900986425
2294 ms 147.50.228.44
9 2026-08-25 03:44 639232255723518075
376 ms 147.50.228.44
8 2026-08-25 03:27 639232245484452890
415 ms 147.50.228.44
7 2026-08-25 03:10 639232235157175331
283 ms 147.50.228.44
6 2026-08-25 02:17 639232203197189095
370 ms 147.50.228.44
5 2026-08-25 02:00 639232192844564298
372 ms 147.50.228.44
4 2026-08-25 01:42 639232182496008942
378 ms 147.50.228.44
3 2026-08-25 01:25 639232172197053132
5 ms 147.50.228.44
2 2026-08-25 00:32 639232140250307418
380 ms 147.50.228.44
1 2026-08-25 00:15 639232129927860324
368 ms 147.50.228.44