DNS response history for ns2.inidanolafamilymedical.com

ns2.inidanolafamilymedical.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-09-01. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 403 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 ns2.inidanolafamilymedical.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

403 ms

Calculated from available response records

Latest Check on Selected Date

2026-09-01 12:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

142.11.227.62

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns2.inidanolafamilymedical.com

Showing DNS history for 2026-09-01 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
37 2026-09-01 12:43 639238628486902752
156 ms 142.11.227.62
36 2026-09-01 12:26 639238617906743100
258 ms 142.11.227.62
35 2026-09-01 12:08 639238607506044626
247 ms 142.11.227.62
34 2026-09-01 11:51 639238597040761406
257 ms 142.11.227.62
33 2026-09-01 11:33 639238586261546969
4 ms 142.11.227.62
32 2026-09-01 11:15 639238575587642333
8 ms 142.11.227.62
31 2026-09-01 10:21 639238543127398267
272 ms 142.11.227.62
30 2026-09-01 10:03 639238532668234016
4 ms 142.11.227.62
29 2026-09-01 09:46 639238522029321761
277 ms 142.11.227.62
28 2026-09-01 09:28 639238511519050351
265 ms 142.11.227.62
27 2026-09-01 09:11 639238500942239673
259 ms 142.11.227.62
26 2026-09-01 08:53 639238490412377398
273 ms 142.11.227.62
25 2026-09-01 08:35 639238479833203021
1688 ms 142.11.227.62
24 2026-09-01 08:18 639238469140507479
255 ms 142.11.227.62
23 2026-09-01 08:00 639238458443560361
250 ms 142.11.227.62
22 2026-09-01 07:42 639238447694851502
249 ms 142.11.227.62
21 2026-09-01 07:24 639238436624109087
261 ms 142.11.227.62
20 2026-09-01 07:05 639238425565611335
264 ms 142.11.227.62
19 2026-09-01 06:10 639238392250222581
259 ms 142.11.227.62
18 2026-09-01 05:51 639238381322537831
136 ms 142.11.227.62
17 2026-09-01 05:33 639238370248186084
257 ms 142.11.227.62
16 2026-09-01 05:15 639238359264687845
1699 ms 142.11.227.62
15 2026-09-01 04:57 639238348534621818
269 ms 142.11.227.62
14 2026-09-01 04:39 639238337725739433
259 ms 142.11.227.62
13 2026-09-01 04:20 639238326844749368
269 ms 142.11.227.62
12 2026-09-01 04:02 639238315792024737
242 ms 142.11.227.62
11 2026-09-01 03:44 639238304931064768
256 ms 142.11.227.62
10 2026-09-01 03:26 639238294131483803
236 ms 142.11.227.62
9 2026-09-01 03:08 639238283314985519
240 ms 142.11.227.62
8 2026-09-01 02:50 639238272374093187
244 ms 142.11.227.62
7 2026-09-01 01:56 639238240032549922
9 ms 142.11.227.62
6 2026-09-01 01:38 639238229204177368
2155 ms 142.11.227.62
5 2026-09-01 01:20 639238218326150282
243 ms 142.11.227.62
4 2026-09-01 01:02 639238207574700853
2129 ms 142.11.227.62
3 2026-09-01 00:43 639238196660283915
246 ms 142.11.227.62
2 2026-09-01 00:25 639238185782358546
237 ms 142.11.227.62
1 2026-09-01 00:07 639238175054391781
267 ms 142.11.227.62