DNS response history for ns2.conservatoriosjdr.com.br

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

30

Historical checks stored for this nameserver on selected date

Average Latency

592 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

179.108.192.137

Most recently resolved hosting IP on selected date

Successful Responses

30

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.conservatoriosjdr.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
30 2026-08-25 10:20 639232492740373468
409 ms 179.108.192.137
29 2026-08-25 10:03 639232482235303141
407 ms 179.108.192.137
28 2026-08-25 09:46 639232471861770303
422 ms 179.108.192.137
27 2026-08-25 09:28 639232461630217327
413 ms 179.108.192.137
26 2026-08-25 09:11 639232451282965990
430 ms 179.108.192.137
25 2026-08-25 08:54 639232440814614938
2355 ms 179.108.192.137
24 2026-08-25 08:37 639232430410720425
419 ms 179.108.192.137
23 2026-08-25 08:19 639232420003096185
431 ms 179.108.192.137
22 2026-08-25 08:02 639232409467287444
425 ms 179.108.192.137
21 2026-08-25 07:44 639232399077195997
420 ms 179.108.192.137
20 2026-08-25 07:27 639232388731528337
423 ms 179.108.192.137
19 2026-08-25 07:10 639232378288598612
423 ms 179.108.192.137
18 2026-08-25 06:16 639232346196373643
3 ms 179.108.192.137
17 2026-08-25 05:59 639232336112370741
241 ms 179.108.192.137
16 2026-08-25 05:42 639232326146508970
418 ms 179.108.192.137
15 2026-08-25 05:26 639232316189381720
414 ms 179.108.192.137
14 2026-08-25 05:09 639232306217998913
426 ms 179.108.192.137
13 2026-08-25 04:53 639232296255744174
408 ms 179.108.192.137
12 2026-08-25 04:36 639232286095760789
416 ms 179.108.192.137
11 2026-08-25 04:19 639232276086186273
2224 ms 179.108.192.137
10 2026-08-25 04:02 639232265900986425
420 ms 179.108.192.137
9 2026-08-25 03:45 639232255723518075
428 ms 179.108.192.137
8 2026-08-25 03:28 639232245484452890
456 ms 179.108.192.137
7 2026-08-25 03:11 639232235157175331
420 ms 179.108.192.137
6 2026-08-25 02:18 639232203197189095
419 ms 179.108.192.137
5 2026-08-25 02:01 639232192844564298
430 ms 179.108.192.137
4 2026-08-25 01:43 639232182496008942
2411 ms 179.108.192.137
3 2026-08-25 01:26 639232172197053132
426 ms 179.108.192.137
2 2026-08-25 00:33 639232140250307418
416 ms 179.108.192.137
1 2026-08-25 00:16 639232129927860324
419 ms 179.108.192.137