DNS response history for ns1.new-phoenix.com

ns1.new-phoenix.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 30 DNS check records, 30 successful responses, 0 failed responses, and 259 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.new-phoenix.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

259 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.101.146.45

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 ns1.new-phoenix.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
30 2026-08-25 10:11 639232492740373468
60 ms 5.101.146.45
29 2026-08-25 09:53 639232482235303141
107 ms 5.101.146.45
28 2026-08-25 09:36 639232471861770303
48 ms 5.101.146.45
27 2026-08-25 09:19 639232461630217327
59 ms 5.101.146.45
26 2026-08-25 09:02 639232451282965990
4053 ms 5.101.146.45
25 2026-08-25 08:44 639232440814614938
48 ms 5.101.146.45
24 2026-08-25 08:27 639232430410720425
77 ms 5.101.146.45
23 2026-08-25 08:10 639232420003096185
71 ms 5.101.146.45
22 2026-08-25 07:52 639232409467287444
55 ms 5.101.146.45
21 2026-08-25 07:35 639232399077195997
31 ms 5.101.146.45
20 2026-08-25 07:17 639232388731528337
60 ms 5.101.146.45
19 2026-08-25 07:00 639232378288598612
183 ms 5.101.146.45
18 2026-08-25 06:07 639232346196373643
2059 ms 5.101.146.45
17 2026-08-25 05:50 639232336112370741
61 ms 5.101.146.45
16 2026-08-25 05:33 639232326146508970
23 ms 5.101.146.45
15 2026-08-25 05:16 639232316189381720
59 ms 5.101.146.45
14 2026-08-25 05:00 639232306217998913
44 ms 5.101.146.45
13 2026-08-25 04:43 639232296255744174
46 ms 5.101.146.45
12 2026-08-25 04:26 639232286095760789
58 ms 5.101.146.45
11 2026-08-25 04:10 639232276086186273
59 ms 5.101.146.45
10 2026-08-25 03:53 639232265900986425
65 ms 5.101.146.45
9 2026-08-25 03:36 639232255723518075
45 ms 5.101.146.45
8 2026-08-25 03:19 639232245484452890
46 ms 5.101.146.45
7 2026-08-25 03:01 639232235157175331
56 ms 5.101.146.45
6 2026-08-25 02:08 639232203197189095
46 ms 5.101.146.45
5 2026-08-25 01:51 639232192844564298
57 ms 5.101.146.45
4 2026-08-25 01:34 639232182496008942
74 ms 5.101.146.45
3 2026-08-25 01:16 639232172197053132
34 ms 5.101.146.45
2 2026-08-25 00:23 639232140250307418
50 ms 5.101.146.45
1 2026-08-25 00:06 639232129927860324
47 ms 5.101.146.45