DNS response history for ns2.crfmt.org.br

ns2.crfmt.org.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 459 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.crfmt.org.br.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

459 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

162.240.110.30

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.crfmt.org.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
178 ms 162.240.110.30
29 2026-08-25 10:03 639232482235303141
2203 ms 162.240.110.30
28 2026-08-25 09:46 639232471861770303
362 ms 162.240.110.30
27 2026-08-25 09:28 639232461630217327
350 ms 162.240.110.30
26 2026-08-25 09:11 639232451282965990
2259 ms 162.240.110.30
25 2026-08-25 08:54 639232440814614938
357 ms 162.240.110.30
24 2026-08-25 08:37 639232430410720425
179 ms 162.240.110.30
23 2026-08-25 08:19 639232420003096185
179 ms 162.240.110.30
22 2026-08-25 08:02 639232409467287444
190 ms 162.240.110.30
21 2026-08-25 07:44 639232399077195997
362 ms 162.240.110.30
20 2026-08-25 07:27 639232388731528337
4 ms 162.240.110.30
19 2026-08-25 07:10 639232378288598612
3 ms 162.240.110.30
18 2026-08-25 06:16 639232346196373643
372 ms 162.240.110.30
17 2026-08-25 05:59 639232336112370741
359 ms 162.240.110.30
16 2026-08-25 05:42 639232326146508970
347 ms 162.240.110.30
15 2026-08-25 05:26 639232316189381720
364 ms 162.240.110.30
14 2026-08-25 05:09 639232306217998913
354 ms 162.240.110.30
13 2026-08-25 04:53 639232296255744174
3 ms 162.240.110.30
12 2026-08-25 04:36 639232286095760789
339 ms 162.240.110.30
11 2026-08-25 04:19 639232276086186273
171 ms 162.240.110.30
10 2026-08-25 04:02 639232265900986425
170 ms 162.240.110.30
9 2026-08-25 03:45 639232255723518075
337 ms 162.240.110.30
8 2026-08-25 03:28 639232245484452890
364 ms 162.240.110.30
7 2026-08-25 03:11 639232235157175331
361 ms 162.240.110.30
6 2026-08-25 02:18 639232203197189095
171 ms 162.240.110.30
5 2026-08-25 02:01 639232192844564298
176 ms 162.240.110.30
4 2026-08-25 01:43 639232182496008942
350 ms 162.240.110.30
3 2026-08-25 01:26 639232172197053132
2194 ms 162.240.110.30
2 2026-08-25 00:33 639232140250307418
346 ms 162.240.110.30
1 2026-08-25 00:16 639232129927860324
352 ms 162.240.110.30