DNS response history for ns2.brindeemcuritiba.com.br

ns2.brindeemcuritiba.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 31 DNS check records, 31 successful responses, 0 failed responses, and 609 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.brindeemcuritiba.com.br.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

609 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

186.202.161.17

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 ns2.brindeemcuritiba.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
31 2026-08-25 10:22 639232492740373468
386 ms 186.202.161.17
30 2026-08-25 10:05 639232482235303141
913 ms 186.202.161.17
29 2026-08-25 09:47 639232471861770303
911 ms 186.202.161.17
28 2026-08-25 09:30 639232461630217327
378 ms 186.202.161.17
27 2026-08-25 09:13 639232451282965990
370 ms 186.202.161.17
26 2026-08-25 08:56 639232440814614938
884 ms 186.202.161.17
25 2026-08-25 08:38 639232430410720425
948 ms 186.202.161.17
24 2026-08-25 08:21 639232420003096185
378 ms 186.202.161.17
23 2026-08-25 08:03 639232409467287444
374 ms 186.202.161.17
22 2026-08-25 07:46 639232399077195997
911 ms 186.202.161.17
21 2026-08-25 07:28 639232388731528337
919 ms 186.202.161.17
20 2026-08-25 07:11 639232378288598612
406 ms 186.202.161.17
19 2026-08-25 06:17 639232346196373643
4 ms 186.202.161.17
18 2026-08-25 06:01 639232336112370741
4 ms 186.202.161.17
17 2026-08-25 05:44 639232326146508970
3 ms 186.202.161.17
16 2026-08-25 05:27 639232316189381720
240 ms 186.202.161.17
15 2026-08-25 05:11 639232306217998913
893 ms 186.202.161.17
14 2026-08-25 04:54 639232296255744174
884 ms 186.202.161.17
13 2026-08-25 04:37 639232286095760789
912 ms 186.202.161.17
12 2026-08-25 04:20 639232276086186273
384 ms 186.202.161.17
11 2026-08-25 04:04 639232265900986425
387 ms 186.202.161.17
10 2026-08-25 03:47 639232255723518075
668 ms 186.202.161.17
9 2026-08-25 03:30 639232245484452890
944 ms 186.202.161.17
8 2026-08-25 03:13 639232235157175331
673 ms 186.202.161.17
7 2026-08-25 02:19 639232203197189095
397 ms 186.202.161.17
6 2026-08-25 02:02 639232192844564298
511 ms 186.202.161.17
5 2026-08-25 01:45 639232182496008942
585 ms 186.202.161.17
4 2026-08-25 01:28 639232172197053132
1924 ms 186.202.161.17
3 2026-08-25 00:34 639232140250307418
398 ms 186.202.161.17
2 2026-08-25 00:17 639232129927860324
395 ms 186.202.161.17
1 2026-08-25 00:00 639232119551972438
904 ms 186.202.161.17