DNS response history for ns1.nergy.team

ns1.nergy.team 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 36 DNS check records, 35 successful responses, 1 failed responses, and 277 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.nergy.team.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

277 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.165.141.14

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.nergy.team

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
36 2026-08-24 15:15 639231807961539652
2057 ms 95.165.141.14
35 2026-08-24 14:58 639231797631669865
241 ms 95.165.141.14
34 2026-08-24 14:05 639231765923559455
139 ms 95.165.141.14
33 2026-08-24 13:48 639231755868832964
195 ms 95.165.141.14
32 2026-08-24 13:31 639231745628278877
132 ms 95.165.141.14
31 2026-08-24 13:14 639231735407682062
240 ms 95.165.141.14
30 2026-08-24 12:21 639231703815441688
155 ms 95.165.141.14
29 2026-08-24 12:04 639231693747052549
56 ms 95.165.141.14
28 2026-08-24 11:48 639231683712487276
221 ms 95.165.141.14
27 2026-08-24 11:31 639231673513573868
229 ms 95.165.141.14
26 2026-08-24 10:38 639231641791249939
136 ms 95.165.141.14
25 2026-08-24 10:21 639231631866211033
131 ms 95.165.141.14
24 2026-08-24 10:04 639231621644955316
129 ms 95.165.141.14
23 2026-08-24 09:47 639231611478799259
175 ms 95.165.141.14
22 2026-08-24 08:55 639231579923718211
202 ms 95.165.141.14
21 2026-08-24 08:38 639231569810702936
171 ms 95.165.141.14
20 2026-08-24 08:21 639231559762411619
2151 ms 95.165.141.14
19 2026-08-24 08:04 639231549663595407
65 ms 95.165.141.14
18 2026-08-24 07:12 639231518076817246
131 ms 95.165.141.14
17 2026-08-24 06:55 639231508078650885
241 ms 95.165.141.14
16 2026-08-24 06:38 639231498210697093
224 ms 95.165.141.14
15 2026-08-24 06:22 639231488109699360
211 ms 95.165.141.14
14 2026-08-24 05:30 639231456772510692
138 ms 95.165.141.14
13 2026-08-24 05:13 639231447084631185
67 ms 95.165.141.14
12 2026-08-24 04:57 639231437208519473
119 ms 95.165.141.14
11 2026-08-24 04:40 639231427209627490
182 ms 95.165.141.14
10 2026-08-24 03:48 639231395791246644
182 ms 95.165.141.14
9 2026-08-24 03:32 639231386075551458
208 ms 95.165.141.14
8 2026-08-24 03:15 639231376208713791
178 ms 95.165.141.14
7 2026-08-24 02:59 639231366170589276
125 ms 95.165.141.14
6 2026-08-24 02:06 639231334732159368
-
5 2026-08-24 01:50 639231325035670078
159 ms 95.165.141.14
4 2026-08-24 01:33 639231315132253837
171 ms 95.165.141.14
3 2026-08-24 01:17 639231305014280808
219 ms 95.165.141.14
2 2026-08-24 00:24 639231273779380675
156 ms 95.165.141.14
1 2026-08-24 00:09 639231264180839154
144 ms 95.165.141.14