DNS response history for multicare.opmonweb.com.br

multicare.opmonweb.com.br 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 396 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 multicare.opmonweb.com.br.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

396 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

179.190.24.68

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 multicare.opmonweb.com.br

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:23 639232566381512620
178 ms 179.190.24.68
34 2026-08-25 12:06 639232556111768563
195 ms 179.190.24.68
33 2026-08-25 11:49 639232545839529039
189 ms 179.190.24.68
32 2026-08-25 11:31 639232535349285207
384 ms 179.190.24.68
31 2026-08-25 11:14 639232524938080723
2412 ms 179.190.24.68
30 2026-08-25 10:20 639232492740373468
178 ms 179.190.24.68
29 2026-08-25 10:03 639232482235303141
190 ms 179.190.24.68
28 2026-08-25 09:45 639232471861770303
192 ms 179.190.24.68
27 2026-08-25 09:28 639232461630217327
178 ms 179.190.24.68
26 2026-08-25 09:11 639232451282965990
179 ms 179.190.24.68
25 2026-08-25 08:54 639232440814614938
390 ms 179.190.24.68
24 2026-08-25 08:36 639232430410720425
192 ms 179.190.24.68
23 2026-08-25 08:19 639232420003096185
355 ms 179.190.24.68
22 2026-08-25 08:02 639232409467287444
389 ms 179.190.24.68
21 2026-08-25 07:44 639232399077195997
359 ms 179.190.24.68
20 2026-08-25 07:27 639232388731528337
194 ms 179.190.24.68
19 2026-08-25 07:09 639232378288598612
359 ms 179.190.24.68
18 2026-08-25 06:16 639232346196373643
365 ms 179.190.24.68
17 2026-08-25 05:59 639232336112370741
398 ms 179.190.24.68
16 2026-08-25 05:42 639232326146508970
371 ms 179.190.24.68
15 2026-08-25 05:26 639232316189381720
17 ms 179.190.24.68
14 2026-08-25 05:09 639232306217998913
176 ms 179.190.24.68
13 2026-08-25 04:53 639232296255744174
189 ms 179.190.24.68
12 2026-08-25 04:36 639232286095760789
175 ms 179.190.24.68
11 2026-08-25 04:19 639232276086186273
364 ms 179.190.24.68
10 2026-08-25 04:02 639232265900986425
176 ms 179.190.24.68
9 2026-08-25 03:45 639232255723518075
349 ms 179.190.24.68
8 2026-08-25 03:28 639232245484452890
179 ms 179.190.24.68
7 2026-08-25 03:11 639232235157175331
363 ms 179.190.24.68
6 2026-08-25 02:18 639232203197189095
362 ms 179.190.24.68
5 2026-08-25 02:01 639232192844564298
177 ms 179.190.24.68
4 2026-08-25 01:43 639232182496008942
389 ms 179.190.24.68
3 2026-08-25 01:26 639232172197053132
366 ms 179.190.24.68
2 2026-08-25 00:33 639232140250307418
174 ms 179.190.24.68
1 2026-08-25 00:16 639232129927860324
2750 ms 179.190.24.68