DNS response history for ns1.elixirnode.net

ns1.elixirnode.net 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 29 DNS check records, 29 successful responses, 0 failed responses, and 317 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.elixirnode.net.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

317 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.251.89.129

Most recently resolved hosting IP on selected date

Successful Responses

29

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.elixirnode.net

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
29 2026-08-27 09:25 639234191649612722
552 ms 198.251.89.129
28 2026-08-27 09:08 639234181105879568
112 ms 198.251.89.129
27 2026-08-27 08:50 639234170713214496
158 ms 198.251.89.129
26 2026-08-27 08:33 639234160341037652
113 ms 198.251.89.129
25 2026-08-27 08:16 639234149799404224
115 ms 198.251.89.129
24 2026-08-27 07:58 639234139553286469
63 ms 198.251.89.129
23 2026-08-27 07:05 639234107183588293
70 ms 198.251.89.129
22 2026-08-27 06:47 639234096905435724
89 ms 198.251.89.129
21 2026-08-27 06:30 639234086579410775
152 ms 198.251.89.129
20 2026-08-27 06:13 639234076291157956
67 ms 198.251.89.129
19 2026-08-27 05:56 639234065981939454
112 ms 198.251.89.129
18 2026-08-27 05:39 639234055548642997
2008 ms 198.251.89.129
17 2026-08-27 05:21 639234045267979603
103 ms 198.251.89.129
16 2026-08-27 05:04 639234034999717463
72 ms 198.251.89.129
15 2026-08-27 04:47 639234024739225358
127 ms 198.251.89.129
14 2026-08-27 04:30 639234014311170162
157 ms 198.251.89.129
13 2026-08-27 04:12 639234003806017640
39 ms 198.251.89.129
12 2026-08-27 03:55 639233993356203030
56 ms 198.251.89.129
11 2026-08-27 03:02 639233961301716608
12 ms 198.251.89.129
10 2026-08-27 02:44 639233950834200647
2088 ms 198.251.89.129
9 2026-08-27 02:27 639233940431849026
130 ms 198.251.89.129
8 2026-08-27 02:10 639233930110596398
2131 ms 198.251.89.129
7 2026-08-27 01:52 639233919705434540
71 ms 198.251.89.129
6 2026-08-27 01:35 639233909452807845
126 ms 198.251.89.129
5 2026-08-27 01:18 639233899096420820
79 ms 198.251.89.129
4 2026-08-27 01:01 639233888707824939
108 ms 198.251.89.129
3 2026-08-27 00:43 639233878461203802
107 ms 198.251.89.129
2 2026-08-27 00:26 639233868060868209
67 ms 198.251.89.129
1 2026-08-27 00:08 639233857450922991
122 ms 198.251.89.129