DNS response history for ns2.xmrfire.net

ns2.xmrfire.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 34 DNS check records, 34 successful responses, 0 failed responses, and 527 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.xmrfire.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

527 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

3.131.105.122

Most recently resolved hosting IP on selected date

Successful Responses

34

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.xmrfire.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
34 2026-08-24 14:03 639231765923559455
4 ms 3.131.105.122
33 2026-08-24 13:47 639231755868832964
19 ms 3.131.105.122
32 2026-08-24 13:30 639231745628278877
106 ms 3.131.105.122
31 2026-08-24 13:12 639231735407682062
105 ms 3.131.105.122
30 2026-08-24 12:20 639231703815441688
199 ms 3.131.105.122
29 2026-08-24 12:03 639231693747052549
121 ms 3.131.105.122
28 2026-08-24 11:46 639231683712487276
2216 ms 3.131.105.122
27 2026-08-24 11:29 639231673513573868
201 ms 3.131.105.122
26 2026-08-24 10:36 639231641791249939
2128 ms 3.131.105.122
25 2026-08-24 10:20 639231631866211033
222 ms 3.131.105.122
24 2026-08-24 10:03 639231621644955316
25 ms 3.131.105.122
23 2026-08-24 09:46 639231611478799259
210 ms 3.131.105.122
22 2026-08-24 08:53 639231579923718211
201 ms 3.131.105.122
21 2026-08-24 08:37 639231569810702936
2117 ms 3.131.105.122
20 2026-08-24 08:19 639231559762411619
209 ms 3.131.105.122
19 2026-08-24 08:03 639231549663595407
2158 ms 3.131.105.122
18 2026-08-24 07:10 639231518076817246
227 ms 3.131.105.122
17 2026-08-24 06:54 639231508078650885
12 ms 3.131.105.122
16 2026-08-24 06:37 639231498210697093
16 ms 3.131.105.122
15 2026-08-24 06:20 639231488109699360
2009 ms 3.131.105.122
14 2026-08-24 05:28 639231456772510692
3 ms 3.131.105.122
13 2026-08-24 05:12 639231447084631185
112 ms 3.131.105.122
12 2026-08-24 04:55 639231437208519473
105 ms 3.131.105.122
11 2026-08-24 04:39 639231427209627490
161 ms 3.131.105.122
10 2026-08-24 03:46 639231395791246644
3 ms 3.131.105.122
9 2026-08-24 03:30 639231386075551458
208 ms 3.131.105.122
8 2026-08-24 03:14 639231376208713791
2135 ms 3.131.105.122
7 2026-08-24 02:57 639231366170589276
2 ms 3.131.105.122
6 2026-08-24 02:05 639231334732159368
215 ms 3.131.105.122
5 2026-08-24 01:48 639231325035670078
2009 ms 3.131.105.122
4 2026-08-24 01:32 639231315132253837
204 ms 3.131.105.122
3 2026-08-24 01:15 639231305014280808
46 ms 3.131.105.122
2 2026-08-24 00:23 639231273779380675
3 ms 3.131.105.122
1 2026-08-24 00:07 639231264180839154
197 ms 3.131.105.122