DNS response history for ns2.rivajs.com

ns2.rivajs.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 34 DNS check records, 34 successful responses, 0 failed responses, and 354 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.rivajs.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

354 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.145.51.102

Most recently resolved hosting IP on selected date

Successful Responses

34

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.rivajs.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
34 2026-08-26 10:42 639233370841350248
284 ms 103.145.51.102
33 2026-08-26 10:25 639233360361507238
376 ms 103.145.51.102
32 2026-08-26 10:08 639233350067824371
273 ms 103.145.51.102
31 2026-08-26 09:51 639233339545274518
144 ms 103.145.51.102
30 2026-08-26 09:33 639233329214918079
279 ms 103.145.51.102
29 2026-08-26 09:16 639233318749762337
596 ms 103.145.51.102
28 2026-08-26 08:58 639233308387917838
267 ms 103.145.51.102
27 2026-08-26 08:41 639233297961740122
278 ms 103.145.51.102
26 2026-08-26 08:24 639233287487159094
266 ms 103.145.51.102
25 2026-08-26 08:06 639233276995531707
288 ms 103.145.51.102
24 2026-08-26 07:49 639233266521568229
281 ms 103.145.51.102
23 2026-08-26 07:31 639233256081047431
281 ms 103.145.51.102
22 2026-08-26 06:37 639233223620132921
293 ms 103.145.51.102
21 2026-08-26 06:20 639233213287814244
130 ms 103.145.51.102
20 2026-08-26 06:03 639233202925983161
571 ms 103.145.51.102
19 2026-08-26 05:45 639233192644780696
266 ms 103.145.51.102
18 2026-08-26 05:28 639233182401183833
278 ms 103.145.51.102
17 2026-08-26 05:11 639233172074181051
280 ms 103.145.51.102
16 2026-08-26 04:54 639233161808421455
540 ms 103.145.51.102
15 2026-08-26 04:37 639233151357344052
281 ms 103.145.51.102
14 2026-08-26 04:19 639233141034116946
335 ms 103.145.51.102
13 2026-08-26 04:02 639233130828334142
136 ms 103.145.51.102
12 2026-08-26 03:45 639233120373450007
283 ms 103.145.51.102
11 2026-08-26 03:28 639233110066216193
279 ms 103.145.51.102
10 2026-08-26 02:35 639233078065410564
271 ms 103.145.51.102
9 2026-08-26 02:17 639233067787457832
567 ms 103.145.51.102
8 2026-08-26 02:00 639233057501801162
274 ms 103.145.51.102
7 2026-08-26 01:43 639233047089431703
275 ms 103.145.51.102
6 2026-08-26 01:26 639233036754790688
270 ms 103.145.51.102
5 2026-08-26 01:09 639233026412602472
262 ms 103.145.51.102
4 2026-08-26 00:51 639233016064066127
276 ms 103.145.51.102
3 2026-08-26 00:34 639233005922655772
2007 ms 103.145.51.102
2 2026-08-26 00:17 639232995672256907
278 ms 103.145.51.102
1 2026-08-26 00:00 639232985300872416
262 ms 103.145.51.102