DNS response history for ns2.phoenix2004.com

ns2.phoenix2004.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-25. For this date, NameServerHistory found 38 DNS check records, 37 successful responses, 1 failed responses, and 336 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.phoenix2004.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

336 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

37.49.151.115

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns2.phoenix2004.com

Showing DNS history for 2026-08-25 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
38 2026-08-25 13:16 639232597643611557
671 ms 37.49.151.115
37 2026-08-25 12:58 639232587225721862
84 ms 37.49.151.115
36 2026-08-25 12:41 639232576780683689
-
35 2026-08-25 12:24 639232566381512620
668 ms 37.49.151.115
34 2026-08-25 12:06 639232556111768563
79 ms 37.49.151.115
33 2026-08-25 11:49 639232545839529039
93 ms 37.49.151.115
32 2026-08-25 11:32 639232535349285207
1560 ms 37.49.151.115
31 2026-08-25 11:14 639232524938080723
82 ms 37.49.151.115
30 2026-08-25 10:21 639232492740373468
84 ms 37.49.151.115
29 2026-08-25 10:04 639232482235303141
662 ms 37.49.151.115
28 2026-08-25 09:46 639232471861770303
79 ms 37.49.151.115
27 2026-08-25 09:29 639232461630217327
93 ms 37.49.151.115
26 2026-08-25 09:12 639232451282965990
1571 ms 37.49.151.115
25 2026-08-25 08:54 639232440814614938
83 ms 37.49.151.115
24 2026-08-25 08:37 639232430410720425
76 ms 37.49.151.115
23 2026-08-25 08:20 639232420003096185
660 ms 37.49.151.115
22 2026-08-25 08:02 639232409467287444
1580 ms 37.49.151.115
21 2026-08-25 07:45 639232399077195997
85 ms 37.49.151.115
20 2026-08-25 07:27 639232388731528337
79 ms 37.49.151.115
19 2026-08-25 07:10 639232378288598612
84 ms 37.49.151.115
18 2026-08-25 06:16 639232346196373643
94 ms 37.49.151.115
17 2026-08-25 05:59 639232336112370741
83 ms 37.49.151.115
16 2026-08-25 05:43 639232326146508970
658 ms 37.49.151.115
15 2026-08-25 05:26 639232316189381720
79 ms 37.49.151.115
14 2026-08-25 05:10 639232306217998913
658 ms 37.49.151.115
13 2026-08-25 04:53 639232296255744174
77 ms 37.49.151.115
12 2026-08-25 04:36 639232286095760789
82 ms 37.49.151.115
11 2026-08-25 04:19 639232276086186273
78 ms 37.49.151.115
10 2026-08-25 04:03 639232265900986425
79 ms 37.49.151.115
9 2026-08-25 03:46 639232255723518075
77 ms 37.49.151.115
8 2026-08-25 03:29 639232245484452890
86 ms 37.49.151.115
7 2026-08-25 03:11 639232235157175331
80 ms 37.49.151.115
6 2026-08-25 02:18 639232203197189095
80 ms 37.49.151.115
5 2026-08-25 02:01 639232192844564298
51 ms 37.49.151.115
4 2026-08-25 01:44 639232182496008942
1542 ms 37.49.151.115
3 2026-08-25 01:26 639232172197053132
82 ms 37.49.151.115
2 2026-08-25 00:33 639232140250307418
81 ms 37.49.151.115
1 2026-08-25 00:16 639232129927860324
88 ms 37.49.151.115