DNS response history for mx1.us.opalstack.com

mx1.us.opalstack.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 31 DNS check records, 31 successful responses, 0 failed responses, and 198 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 mx1.us.opalstack.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

198 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.62.123.121

Most recently resolved hosting IP on selected date

Successful Responses

31

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 mx1.us.opalstack.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
31 2026-08-26 10:00 639233350067824371
177 ms 108.62.123.121
30 2026-08-26 09:43 639233339545274518
18 ms 108.62.123.121
29 2026-08-26 09:26 639233329214918079
15 ms 108.62.123.121
28 2026-08-26 09:08 639233318749762337
21 ms 108.62.123.121
27 2026-08-26 08:51 639233308387917838
16 ms 108.62.123.121
26 2026-08-26 08:33 639233297961740122
32 ms 108.62.123.121
25 2026-08-26 08:16 639233287487159094
94 ms 108.62.123.121
24 2026-08-26 07:58 639233276995531707
303 ms 108.62.123.121
23 2026-08-26 07:41 639233266521568229
2027 ms 108.62.123.121
22 2026-08-26 07:24 639233256081047431
31 ms 108.62.123.121
21 2026-08-26 06:30 639233223620132921
20 ms 108.62.123.121
20 2026-08-26 06:12 639233213287814244
18 ms 108.62.123.121
19 2026-08-26 05:55 639233202925983161
2033 ms 108.62.123.121
18 2026-08-26 05:38 639233192644780696
40 ms 108.62.123.121
17 2026-08-26 05:21 639233182401183833
36 ms 108.62.123.121
16 2026-08-26 05:04 639233172074181051
255 ms 108.62.123.121
15 2026-08-26 04:47 639233161808421455
39 ms 108.62.123.121
14 2026-08-26 04:29 639233151357344052
29 ms 108.62.123.121
13 2026-08-26 04:12 639233141034116946
126 ms 108.62.123.121
12 2026-08-26 03:55 639233130828334142
15 ms 108.62.123.121
11 2026-08-26 03:37 639233120373450007
25 ms 108.62.123.121
10 2026-08-26 03:20 639233110066216193
19 ms 108.62.123.121
9 2026-08-26 02:27 639233078065410564
5 ms 108.62.123.121
8 2026-08-26 02:10 639233067787457832
21 ms 108.62.123.121
7 2026-08-26 01:53 639233057501801162
3 ms 108.62.123.121
6 2026-08-26 01:35 639233047089431703
18 ms 108.62.123.121
5 2026-08-26 01:18 639233036754790688
43 ms 108.62.123.121
4 2026-08-26 01:01 639233026412602472
549 ms 108.62.123.121
3 2026-08-26 00:44 639233016064066127
40 ms 108.62.123.121
2 2026-08-26 00:27 639233005922655772
42 ms 108.62.123.121
1 2026-08-26 00:10 639232995672256907
39 ms 108.62.123.121