DNS response history for ns1.rifycloud.com

ns1.rifycloud.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-27. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 351 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.rifycloud.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

351 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.50.160.20

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.rifycloud.com

Showing DNS history for 2026-08-27 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-27 12:07 639234286253196126
284 ms 103.50.160.20
35 2026-08-27 11:13 639234253963286387
3 ms 103.50.160.20
34 2026-08-27 10:56 639234243654907465
3 ms 103.50.160.20
33 2026-08-27 10:39 639234233269654413
274 ms 103.50.160.20
32 2026-08-27 10:22 639234222943951923
275 ms 103.50.160.20
31 2026-08-27 10:04 639234212558002823
289 ms 103.50.160.20
30 2026-08-27 09:47 639234202117531850
267 ms 103.50.160.20
29 2026-08-27 09:30 639234191649612722
288 ms 103.50.160.20
28 2026-08-27 09:12 639234181105879568
281 ms 103.50.160.20
27 2026-08-27 08:55 639234170713214496
280 ms 103.50.160.20
26 2026-08-27 08:37 639234160341037652
282 ms 103.50.160.20
25 2026-08-27 08:20 639234149799404224
277 ms 103.50.160.20
24 2026-08-27 08:02 639234139553286469
286 ms 103.50.160.20
23 2026-08-27 07:09 639234107183588293
259 ms 103.50.160.20
22 2026-08-27 06:52 639234096905435724
277 ms 103.50.160.20
21 2026-08-27 06:35 639234086579410775
266 ms 103.50.160.20
20 2026-08-27 06:17 639234076291157956
271 ms 103.50.160.20
19 2026-08-27 06:00 639234065981939454
2192 ms 103.50.160.20
18 2026-08-27 05:43 639234055548642997
285 ms 103.50.160.20
17 2026-08-27 05:26 639234045267979603
2143 ms 103.50.160.20
16 2026-08-27 05:09 639234034999717463
280 ms 103.50.160.20
15 2026-08-27 04:51 639234024739225358
271 ms 103.50.160.20
14 2026-08-27 04:34 639234014311170162
272 ms 103.50.160.20
13 2026-08-27 04:17 639234003806017640
273 ms 103.50.160.20
12 2026-08-27 03:59 639233993356203030
280 ms 103.50.160.20
11 2026-08-27 03:06 639233961301716608
266 ms 103.50.160.20
10 2026-08-27 02:49 639233950834200647
283 ms 103.50.160.20
9 2026-08-27 02:31 639233940431849026
280 ms 103.50.160.20
8 2026-08-27 02:14 639233930110596398
4 ms 103.50.160.20
7 2026-08-27 01:57 639233919705434540
267 ms 103.50.160.20
6 2026-08-27 01:39 639233909452807845
3 ms 103.50.160.20
5 2026-08-27 01:22 639233899096420820
278 ms 103.50.160.20
4 2026-08-27 01:05 639233888707824939
276 ms 103.50.160.20
3 2026-08-27 00:48 639233878461203802
271 ms 103.50.160.20
2 2026-08-27 00:30 639233868060868209
266 ms 103.50.160.20
1 2026-08-27 00:13 639233857450922991
270 ms 103.50.160.20