DNS response history for ns1.rio333.net

ns1.rio333.net 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 36 DNS check records, 36 successful responses, 0 failed responses, and 233 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.rio333.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

233 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.57.160.111

Most recently resolved hosting IP on selected date

Successful Responses

36

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.rio333.net

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
36 2026-08-25 12:26 639232566381512620
3 ms 69.57.160.111
35 2026-08-25 12:08 639232556111768563
7 ms 69.57.160.111
34 2026-08-25 11:51 639232545839529039
324 ms 69.57.160.111
33 2026-08-25 11:34 639232535349285207
5 ms 69.57.160.111
32 2026-08-25 11:16 639232524938080723
3 ms 69.57.160.111
31 2026-08-25 10:23 639232492740373468
5 ms 69.57.160.111
30 2026-08-25 10:06 639232482235303141
4 ms 69.57.160.111
29 2026-08-25 09:48 639232471861770303
313 ms 69.57.160.111
28 2026-08-25 09:31 639232461630217327
307 ms 69.57.160.111
27 2026-08-25 09:14 639232451282965990
310 ms 69.57.160.111
26 2026-08-25 08:56 639232440814614938
312 ms 69.57.160.111
25 2026-08-25 08:39 639232430410720425
309 ms 69.57.160.111
24 2026-08-25 08:22 639232420003096185
300 ms 69.57.160.111
23 2026-08-25 08:04 639232409467287444
321 ms 69.57.160.111
22 2026-08-25 07:47 639232399077195997
307 ms 69.57.160.111
21 2026-08-25 07:29 639232388731528337
311 ms 69.57.160.111
20 2026-08-25 07:12 639232378288598612
310 ms 69.57.160.111
19 2026-08-25 06:18 639232346196373643
314 ms 69.57.160.111
18 2026-08-25 06:01 639232336112370741
305 ms 69.57.160.111
17 2026-08-25 05:45 639232326146508970
3 ms 69.57.160.111
16 2026-08-25 05:28 639232316189381720
308 ms 69.57.160.111
15 2026-08-25 05:12 639232306217998913
3 ms 69.57.160.111
14 2026-08-25 04:55 639232296255744174
304 ms 69.57.160.111
13 2026-08-25 04:38 639232286095760789
3 ms 69.57.160.111
12 2026-08-25 04:21 639232276086186273
300 ms 69.57.160.111
11 2026-08-25 04:05 639232265900986425
313 ms 69.57.160.111
10 2026-08-25 03:48 639232255723518075
318 ms 69.57.160.111
9 2026-08-25 03:31 639232245484452890
308 ms 69.57.160.111
8 2026-08-25 03:14 639232235157175331
296 ms 69.57.160.111
7 2026-08-25 02:20 639232203197189095
308 ms 69.57.160.111
6 2026-08-25 02:03 639232192844564298
312 ms 69.57.160.111
5 2026-08-25 01:46 639232182496008942
306 ms 69.57.160.111
4 2026-08-25 01:28 639232172197053132
301 ms 69.57.160.111
3 2026-08-25 00:35 639232140250307418
301 ms 69.57.160.111
2 2026-08-25 00:18 639232129927860324
305 ms 69.57.160.111
1 2026-08-25 00:01 639232119551972438
314 ms 69.57.160.111