DNS response history for ns5.redorum.com

ns5.redorum.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-31. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 186 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 ns5.redorum.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

186 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-31 12:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.80.127.4

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns5.redorum.com

Showing DNS history for 2026-08-31 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
37 2026-08-31 12:15 639237753225101103
18 ms 208.80.127.4
36 2026-08-31 11:58 639237742927117371
24 ms 208.80.127.4
35 2026-08-31 11:41 639237732538256235
2028 ms 208.80.127.4
34 2026-08-31 11:23 639237722025682013
20 ms 208.80.127.4
33 2026-08-31 11:06 639237711568720101
35 ms 208.80.127.4
32 2026-08-31 10:48 639237701119461876
28 ms 208.80.127.4
31 2026-08-31 10:31 639237690759595513
23 ms 208.80.127.4
30 2026-08-31 10:13 639237680122296836
18 ms 208.80.127.4
29 2026-08-31 09:20 639237647999458954
20 ms 208.80.127.4
28 2026-08-31 09:03 639237637680951774
20 ms 208.80.127.4
27 2026-08-31 08:46 639237627437728712
54 ms 208.80.127.4
26 2026-08-31 08:28 639237617127808241
29 ms 208.80.127.4
25 2026-08-31 08:12 639237606990101394
27 ms 208.80.127.4
24 2026-08-31 07:54 639237596595480036
2030 ms 208.80.127.4
23 2026-08-31 07:37 639237586261012001
34 ms 208.80.127.4
22 2026-08-31 07:20 639237576047657695
18 ms 208.80.127.4
21 2026-08-31 07:03 639237565832936443
32 ms 208.80.127.4
20 2026-08-31 06:46 639237555466329546
29 ms 208.80.127.4
19 2026-08-31 06:28 639237545032411072
22 ms 208.80.127.4
18 2026-08-31 06:11 639237534469438634
18 ms 208.80.127.4
17 2026-08-31 05:17 639237502279296801
19 ms 208.80.127.4
16 2026-08-31 05:00 639237492362730124
13 ms 208.80.127.4
15 2026-08-31 04:44 639237482311584319
9 ms 208.80.127.4
14 2026-08-31 04:27 639237472150685594
19 ms 208.80.127.4
13 2026-08-31 04:10 639237462055295430
46 ms 208.80.127.4
12 2026-08-31 03:53 639237452089913890
15 ms 208.80.127.4
11 2026-08-31 03:37 639237441972654103
19 ms 208.80.127.4
10 2026-08-31 03:20 639237432052396478
15 ms 208.80.127.4
9 2026-08-31 03:03 639237422012990851
13 ms 208.80.127.4
8 2026-08-31 02:46 639237411889602012
12 ms 208.80.127.4
7 2026-08-31 02:29 639237401637354221
57 ms 208.80.127.4
6 2026-08-31 02:12 639237391412690360
24 ms 208.80.127.4
5 2026-08-31 01:20 639237359972957132
12 ms 208.80.127.4
4 2026-08-31 01:03 639237350032183979
13 ms 208.80.127.4
3 2026-08-31 00:47 639237340111452066
2020 ms 208.80.127.4
2 2026-08-31 00:30 639237329967272514
17 ms 208.80.127.4
1 2026-08-31 00:13 639237319916508151
19 ms 208.80.127.4