DNS response history for ns2.xtreemly.net

ns2.xtreemly.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-24. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 492 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 ns2.xtreemly.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

492 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

135.148.4.31

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns2.xtreemly.net

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
30 2026-08-24 12:20 639231703815441688
147 ms 135.148.4.31
29 2026-08-24 12:04 639231693747052549
241 ms 135.148.4.31
28 2026-08-24 11:47 639231683712487276
277 ms 135.148.4.31
27 2026-08-24 11:30 639231673513573868
2009 ms 135.148.4.31
26 2026-08-24 10:37 639231641791249939
207 ms 135.148.4.31
25 2026-08-24 10:20 639231631866211033
208 ms 135.148.4.31
24 2026-08-24 10:04 639231621644955316
211 ms 135.148.4.31
23 2026-08-24 09:46 639231611478799259
104 ms 135.148.4.31
22 2026-08-24 08:54 639231579923718211
2112 ms 135.148.4.31
21 2026-08-24 08:37 639231569810702936
210 ms 135.148.4.31
20 2026-08-24 08:20 639231559762411619
235 ms 135.148.4.31
19 2026-08-24 08:03 639231549663595407
104 ms 135.148.4.31
18 2026-08-24 07:11 639231518076817246
206 ms 135.148.4.31
17 2026-08-24 06:54 639231508078650885
103 ms 135.148.4.31
16 2026-08-24 06:38 639231498210697093
149 ms 135.148.4.31
15 2026-08-24 06:21 639231488109699360
213 ms 135.148.4.31
14 2026-08-24 05:29 639231456772510692
135 ms 135.148.4.31
13 2026-08-24 05:13 639231447084631185
108 ms 135.148.4.31
12 2026-08-24 04:56 639231437208519473
127 ms 135.148.4.31
11 2026-08-24 04:39 639231427209627490
2101 ms 135.148.4.31
10 2026-08-24 03:47 639231395791246644
205 ms 135.148.4.31
9 2026-08-24 03:31 639231386075551458
2099 ms 135.148.4.31
8 2026-08-24 03:15 639231376208713791
258 ms 135.148.4.31
7 2026-08-24 02:58 639231366170589276
119 ms 135.148.4.31
6 2026-08-24 02:05 639231334732159368
121 ms 135.148.4.31
5 2026-08-24 01:49 639231325035670078
2126 ms 135.148.4.31
4 2026-08-24 01:33 639231315132253837
103 ms 135.148.4.31
3 2026-08-24 01:16 639231305014280808
205 ms 135.148.4.31
2 2026-08-24 00:24 639231273779380675
217 ms 135.148.4.31
1 2026-08-24 00:08 639231264180839154
102 ms 135.148.4.31