DNS response history for ns1.rg3.com.br

ns1.rg3.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 530 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 ns1.rg3.com.br.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

530 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

177.73.238.135

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 ns1.rg3.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
371 ms 177.73.238.135
29 2026-08-25 10:03 639232482235303141
184 ms 177.73.238.135
28 2026-08-25 09:45 639232471861770303
381 ms 177.73.238.135
27 2026-08-25 09:28 639232461630217327
373 ms 177.73.238.135
26 2026-08-25 09:11 639232451282965990
383 ms 177.73.238.135
25 2026-08-25 08:54 639232440814614938
2031 ms 177.73.238.135
24 2026-08-25 08:36 639232430410720425
374 ms 177.73.238.135
23 2026-08-25 08:19 639232420003096185
187 ms 177.73.238.135
22 2026-08-25 08:02 639232409467287444
369 ms 177.73.238.135
21 2026-08-25 07:44 639232399077195997
368 ms 177.73.238.135
20 2026-08-25 07:27 639232388731528337
374 ms 177.73.238.135
19 2026-08-25 07:09 639232378288598612
371 ms 177.73.238.135
18 2026-08-25 06:16 639232346196373643
2 ms 177.73.238.135
17 2026-08-25 05:59 639232336112370741
2 ms 177.73.238.135
16 2026-08-25 05:42 639232326146508970
2504 ms 177.73.238.135
15 2026-08-25 05:26 639232316189381720
4 ms 177.73.238.135
14 2026-08-25 05:09 639232306217998913
4 ms 177.73.238.135
13 2026-08-25 04:53 639232296255744174
4 ms 177.73.238.135
12 2026-08-25 04:36 639232286095760789
362 ms 177.73.238.135
11 2026-08-25 04:19 639232276086186273
178 ms 177.73.238.135
10 2026-08-25 04:02 639232265900986425
382 ms 177.73.238.135
9 2026-08-25 03:45 639232255723518075
380 ms 177.73.238.135
8 2026-08-25 03:28 639232245484452890
2225 ms 177.73.238.135
7 2026-08-25 03:11 639232235157175331
385 ms 177.73.238.135
6 2026-08-25 02:18 639232203197189095
372 ms 177.73.238.135
5 2026-08-25 02:01 639232192844564298
369 ms 177.73.238.135
4 2026-08-25 01:43 639232182496008942
2218 ms 177.73.238.135
3 2026-08-25 01:26 639232172197053132
369 ms 177.73.238.135
2 2026-08-25 00:33 639232140250307418
10 ms 177.73.238.135
1 2026-08-25 00:16 639232129927860324
376 ms 177.73.238.135