DNS response history for ns2.medicocaresupport.com

ns2.medicocaresupport.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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 285 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.medicocaresupport.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

285 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.214.175.153

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

Showing DNS history for 2026-08-27 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-27 11:14 639234253963286387
3 ms 74.214.175.153
34 2026-08-27 10:57 639234243654907465
298 ms 74.214.175.153
33 2026-08-27 10:40 639234233269654413
309 ms 74.214.175.153
32 2026-08-27 10:22 639234222943951923
155 ms 74.214.175.153
31 2026-08-27 10:05 639234212558002823
301 ms 74.214.175.153
30 2026-08-27 09:48 639234202117531850
300 ms 74.214.175.153
29 2026-08-27 09:30 639234191649612722
300 ms 74.214.175.153
28 2026-08-27 09:13 639234181105879568
2170 ms 74.214.175.153
27 2026-08-27 08:55 639234170713214496
301 ms 74.214.175.153
26 2026-08-27 08:38 639234160341037652
155 ms 74.214.175.153
25 2026-08-27 08:21 639234149799404224
152 ms 74.214.175.153
24 2026-08-27 08:03 639234139553286469
306 ms 74.214.175.153
23 2026-08-27 07:09 639234107183588293
305 ms 74.214.175.153
22 2026-08-27 06:52 639234096905435724
303 ms 74.214.175.153
21 2026-08-27 06:35 639234086579410775
153 ms 74.214.175.153
20 2026-08-27 06:18 639234076291157956
302 ms 74.214.175.153
19 2026-08-27 06:01 639234065981939454
300 ms 74.214.175.153
18 2026-08-27 05:44 639234055548642997
298 ms 74.214.175.153
17 2026-08-27 05:26 639234045267979603
294 ms 74.214.175.153
16 2026-08-27 05:09 639234034999717463
153 ms 74.214.175.153
15 2026-08-27 04:52 639234024739225358
303 ms 74.214.175.153
14 2026-08-27 04:35 639234014311170162
154 ms 74.214.175.153
13 2026-08-27 04:17 639234003806017640
158 ms 74.214.175.153
12 2026-08-27 04:00 639233993356203030
203 ms 74.214.175.153
11 2026-08-27 03:06 639233961301716608
152 ms 74.214.175.153
10 2026-08-27 02:49 639233950834200647
3 ms 74.214.175.153
9 2026-08-27 02:32 639233940431849026
149 ms 74.214.175.153
8 2026-08-27 02:14 639233930110596398
2 ms 74.214.175.153
7 2026-08-27 01:57 639233919705434540
296 ms 74.214.175.153
6 2026-08-27 01:40 639233909452807845
309 ms 74.214.175.153
5 2026-08-27 01:23 639233899096420820
298 ms 74.214.175.153
4 2026-08-27 01:06 639233888707824939
153 ms 74.214.175.153
3 2026-08-27 00:48 639233878461203802
295 ms 74.214.175.153
2 2026-08-27 00:31 639233868060868209
306 ms 74.214.175.153
1 2026-08-27 00:13 639233857450922991
319 ms 74.214.175.153