DNS response history for ns04.rhyno365.com

ns04.rhyno365.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 35 DNS check records, 35 successful responses, 0 failed responses, and 132 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 ns04.rhyno365.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

132 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

70.35.121.121

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns04.rhyno365.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
35 2026-08-27 11:03 639234253963286387
6 ms 70.35.121.121
34 2026-08-27 10:46 639234243654907465
12 ms 70.35.121.121
33 2026-08-27 10:28 639234233269654413
13 ms 70.35.121.121
32 2026-08-27 10:11 639234222943951923
7 ms 70.35.121.121
31 2026-08-27 09:54 639234212558002823
13 ms 70.35.121.121
30 2026-08-27 09:36 639234202117531850
5 ms 70.35.121.121
29 2026-08-27 09:19 639234191649612722
11 ms 70.35.121.121
28 2026-08-27 09:01 639234181105879568
28 ms 70.35.121.121
27 2026-08-27 08:44 639234170713214496
14 ms 70.35.121.121
26 2026-08-27 08:27 639234160341037652
10 ms 70.35.121.121
25 2026-08-27 08:09 639234149799404224
10 ms 70.35.121.121
24 2026-08-27 07:52 639234139553286469
9 ms 70.35.121.121
23 2026-08-27 06:58 639234107183588293
41 ms 70.35.121.121
22 2026-08-27 06:41 639234096905435724
33 ms 70.35.121.121
21 2026-08-27 06:24 639234086579410775
7 ms 70.35.121.121
20 2026-08-27 06:07 639234076291157956
17 ms 70.35.121.121
19 2026-08-27 05:50 639234065981939454
24 ms 70.35.121.121
18 2026-08-27 05:32 639234055548642997
27 ms 70.35.121.121
17 2026-08-27 05:15 639234045267979603
8 ms 70.35.121.121
16 2026-08-27 04:58 639234034999717463
5 ms 70.35.121.121
15 2026-08-27 04:41 639234024739225358
5 ms 70.35.121.121
14 2026-08-27 04:23 639234014311170162
5 ms 70.35.121.121
13 2026-08-27 04:06 639234003806017640
14 ms 70.35.121.121
12 2026-08-27 03:49 639233993356203030
4030 ms 70.35.121.121
11 2026-08-27 02:55 639233961301716608
13 ms 70.35.121.121
10 2026-08-27 02:38 639233950834200647
16 ms 70.35.121.121
9 2026-08-27 02:20 639233940431849026
36 ms 70.35.121.121
8 2026-08-27 02:03 639233930110596398
13 ms 70.35.121.121
7 2026-08-27 01:46 639233919705434540
56 ms 70.35.121.121
6 2026-08-27 01:29 639233909452807845
51 ms 70.35.121.121
5 2026-08-27 01:11 639233899096420820
27 ms 70.35.121.121
4 2026-08-27 00:54 639233888707824939
14 ms 70.35.121.121
3 2026-08-27 00:37 639233878461203802
4 ms 70.35.121.121
2 2026-08-27 00:20 639233868060868209
7 ms 70.35.121.121
1 2026-08-27 00:02 639233857450922991
32 ms 70.35.121.121