DNS response history for ns1.relymx.com

ns1.relymx.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-24. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 136 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.relymx.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

136 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.136.96.111

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 ns1.relymx.com

Showing DNS history for 2026-08-24 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-24 14:53 639231797631669865
10 ms 185.136.96.111
34 2026-08-24 14:00 639231765923559455
7 ms 185.136.96.111
33 2026-08-24 13:44 639231755868832964
7 ms 185.136.96.111
32 2026-08-24 13:27 639231745628278877
26 ms 185.136.96.111
31 2026-08-24 13:09 639231735407682062
31 ms 185.136.96.111
30 2026-08-24 12:17 639231703815441688
5 ms 185.136.96.111
29 2026-08-24 12:00 639231693747052549
42 ms 185.136.96.111
28 2026-08-24 11:43 639231683712487276
14 ms 185.136.96.111
27 2026-08-24 11:26 639231673513573868
48 ms 185.136.96.111
26 2026-08-24 10:33 639231641791249939
8 ms 185.136.96.111
25 2026-08-24 10:17 639231631866211033
9 ms 185.136.96.111
24 2026-08-24 10:00 639231621644955316
31 ms 185.136.96.111
23 2026-08-24 09:43 639231611478799259
5 ms 185.136.96.111
22 2026-08-24 08:51 639231579923718211
16 ms 185.136.96.111
21 2026-08-24 08:34 639231569810702936
6 ms 185.136.96.111
20 2026-08-24 08:17 639231559762411619
51 ms 185.136.96.111
19 2026-08-24 08:00 639231549663595407
8 ms 185.136.96.111
18 2026-08-24 07:07 639231518076817246
31 ms 185.136.96.111
17 2026-08-24 06:51 639231508078650885
7 ms 185.136.96.111
16 2026-08-24 06:34 639231498210697093
6 ms 185.136.96.111
15 2026-08-24 06:17 639231488109699360
23 ms 185.136.96.111
14 2026-08-24 05:25 639231456772510692
43 ms 185.136.96.111
13 2026-08-24 05:09 639231447084631185
10 ms 185.136.96.111
12 2026-08-24 04:53 639231437208519473
9 ms 185.136.96.111
11 2026-08-24 04:36 639231427209627490
34 ms 185.136.96.111
10 2026-08-24 03:43 639231395791246644
21 ms 185.136.96.111
9 2026-08-24 03:27 639231386075551458
47 ms 185.136.96.111
8 2026-08-24 03:11 639231376208713791
7 ms 185.136.96.111
7 2026-08-24 02:54 639231366170589276
9 ms 185.136.96.111
6 2026-08-24 02:02 639231334732159368
24 ms 185.136.96.111
5 2026-08-24 01:46 639231325035670078
11 ms 185.136.96.111
4 2026-08-24 01:29 639231315132253837
35 ms 185.136.96.111
3 2026-08-24 01:12 639231305014280808
45 ms 185.136.96.111
2 2026-08-24 00:20 639231273779380675
4045 ms 185.136.96.111
1 2026-08-24 00:04 639231264180839154
17 ms 185.136.96.111