DNS response history for ns1.clinicaresearch.com

ns1.clinicaresearch.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 292 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.clinicaresearch.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

292 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.50.161.233

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 ns1.clinicaresearch.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:20 639232566381512620
292 ms 103.50.161.233
34 2026-08-25 12:03 639232556111768563
10 ms 103.50.161.233
33 2026-08-25 11:46 639232545839529039
7 ms 103.50.161.233
32 2026-08-25 11:29 639232535349285207
277 ms 103.50.161.233
31 2026-08-25 11:11 639232524938080723
299 ms 103.50.161.233
30 2026-08-25 10:18 639232492740373468
157 ms 103.50.161.233
29 2026-08-25 10:01 639232482235303141
276 ms 103.50.161.233
28 2026-08-25 09:43 639232471861770303
276 ms 103.50.161.233
27 2026-08-25 09:26 639232461630217327
272 ms 103.50.161.233
26 2026-08-25 09:09 639232451282965990
279 ms 103.50.161.233
25 2026-08-25 08:51 639232440814614938
267 ms 103.50.161.233
24 2026-08-25 08:34 639232430410720425
282 ms 103.50.161.233
23 2026-08-25 08:17 639232420003096185
270 ms 103.50.161.233
22 2026-08-25 07:59 639232409467287444
283 ms 103.50.161.233
21 2026-08-25 07:42 639232399077195997
277 ms 103.50.161.233
20 2026-08-25 07:24 639232388731528337
266 ms 103.50.161.233
19 2026-08-25 07:07 639232378288598612
263 ms 103.50.161.233
18 2026-08-25 06:13 639232346196373643
145 ms 103.50.161.233
17 2026-08-25 05:56 639232336112370741
278 ms 103.50.161.233
16 2026-08-25 05:40 639232326146508970
268 ms 103.50.161.233
15 2026-08-25 05:23 639232316189381720
2165 ms 103.50.161.233
14 2026-08-25 05:07 639232306217998913
2 ms 103.50.161.233
13 2026-08-25 04:50 639232296255744174
272 ms 103.50.161.233
12 2026-08-25 04:33 639232286095760789
4 ms 103.50.161.233
11 2026-08-25 04:16 639232276086186273
280 ms 103.50.161.233
10 2026-08-25 04:00 639232265900986425
280 ms 103.50.161.233
9 2026-08-25 03:43 639232255723518075
155 ms 103.50.161.233
8 2026-08-25 03:26 639232245484452890
201 ms 103.50.161.233
7 2026-08-25 03:08 639232235157175331
311 ms 103.50.161.233
6 2026-08-25 02:15 639232203197189095
310 ms 103.50.161.233
5 2026-08-25 01:58 639232192844564298
324 ms 103.50.161.233
4 2026-08-25 01:41 639232182496008942
299 ms 103.50.161.233
3 2026-08-25 01:23 639232172197053132
306 ms 103.50.161.233
2 2026-08-25 00:30 639232140250307418
292 ms 103.50.161.233
1 2026-08-25 00:13 639232129927860324
267 ms 103.50.161.233