DNS response history for ns.ridata.com

ns.ridata.com 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-26. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 597 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 ns.ridata.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

597 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.39.222.62

Most recently resolved hosting IP on selected date

Successful Responses

27

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 ns.ridata.com

Showing DNS history for 2026-08-26 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
27 2026-08-26 08:44 639233297961740122
3 ms 202.39.222.62
26 2026-08-26 08:26 639233287487159094
710 ms 202.39.222.62
25 2026-08-26 08:09 639233276995531707
694 ms 202.39.222.62
24 2026-08-26 07:52 639233266521568229
301 ms 202.39.222.62
23 2026-08-26 07:34 639233256081047431
682 ms 202.39.222.62
22 2026-08-26 06:40 639233223620132921
574 ms 202.39.222.62
21 2026-08-26 06:23 639233213287814244
618 ms 202.39.222.62
20 2026-08-26 06:05 639233202925983161
591 ms 202.39.222.62
19 2026-08-26 05:48 639233192644780696
646 ms 202.39.222.62
18 2026-08-26 05:31 639233182401183833
604 ms 202.39.222.62
17 2026-08-26 05:14 639233172074181051
632 ms 202.39.222.62
16 2026-08-26 04:57 639233161808421455
604 ms 202.39.222.62
15 2026-08-26 04:40 639233151357344052
593 ms 202.39.222.62
14 2026-08-26 04:22 639233141034116946
583 ms 202.39.222.62
13 2026-08-26 04:05 639233130828334142
679 ms 202.39.222.62
12 2026-08-26 03:48 639233120373450007
591 ms 202.39.222.62
11 2026-08-26 03:31 639233110066216193
1267 ms 202.39.222.62
10 2026-08-26 02:37 639233078065410564
591 ms 202.39.222.62
9 2026-08-26 02:20 639233067787457832
580 ms 202.39.222.62
8 2026-08-26 02:03 639233057501801162
637 ms 202.39.222.62
7 2026-08-26 01:46 639233047089431703
582 ms 202.39.222.62
6 2026-08-26 01:29 639233036754790688
616 ms 202.39.222.62
5 2026-08-26 01:11 639233026412602472
594 ms 202.39.222.62
4 2026-08-26 00:54 639233016064066127
589 ms 202.39.222.62
3 2026-08-26 00:37 639233005922655772
367 ms 202.39.222.62
2 2026-08-26 00:20 639232995672256907
601 ms 202.39.222.62
1 2026-08-26 00:03 639232985300872416
582 ms 202.39.222.62