DNS response history for ns2.phoenixtv.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

374 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.233.29.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.phoenixtv.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
34 2026-08-25 12:01 639232556111768563
12 ms 49.233.29.122
33 2026-08-25 11:44 639232545839529039
220 ms 49.233.29.122
32 2026-08-25 11:26 639232535349285207
217 ms 49.233.29.122
31 2026-08-25 11:09 639232524938080723
2015 ms 49.233.29.122
30 2026-08-25 10:15 639232492740373468
47 ms 49.233.29.122
29 2026-08-25 09:58 639232482235303141
2017 ms 49.233.29.122
28 2026-08-25 09:40 639232471861770303
25 ms 49.233.29.122
27 2026-08-25 09:23 639232461630217327
22 ms 49.233.29.122
26 2026-08-25 09:06 639232451282965990
35 ms 49.233.29.122
25 2026-08-25 08:49 639232440814614938
46 ms 49.233.29.122
24 2026-08-25 08:31 639232430410720425
19 ms 49.233.29.122
23 2026-08-25 08:14 639232420003096185
12 ms 49.233.29.122
22 2026-08-25 07:56 639232409467287444
35 ms 49.233.29.122
21 2026-08-25 07:39 639232399077195997
23 ms 49.233.29.122
20 2026-08-25 07:22 639232388731528337
29 ms 49.233.29.122
19 2026-08-25 07:04 639232378288598612
20 ms 49.233.29.122
18 2026-08-25 06:11 639232346196373643
45 ms 49.233.29.122
17 2026-08-25 05:54 639232336112370741
13 ms 49.233.29.122
16 2026-08-25 05:37 639232326146508970
13 ms 49.233.29.122
15 2026-08-25 05:21 639232316189381720
45 ms 49.233.29.122
14 2026-08-25 05:04 639232306217998913
295 ms 49.233.29.122
13 2026-08-25 04:48 639232296255744174
2020 ms 49.233.29.122
12 2026-08-25 04:31 639232286095760789
276 ms 49.233.29.122
11 2026-08-25 04:14 639232276086186273
18 ms 49.233.29.122
10 2026-08-25 03:57 639232265900986425
307 ms 49.233.29.122
9 2026-08-25 03:40 639232255723518075
12 ms 49.233.29.122
8 2026-08-25 03:23 639232245484452890
20 ms 49.233.29.122
7 2026-08-25 03:06 639232235157175331
17 ms 49.233.29.122
6 2026-08-25 02:13 639232203197189095
265 ms 49.233.29.122
5 2026-08-25 01:55 639232192844564298
14 ms 49.233.29.122
4 2026-08-25 01:38 639232182496008942
27 ms 49.233.29.122
3 2026-08-25 01:21 639232172197053132
2268 ms 49.233.29.122
2 2026-08-25 00:27 639232140250307418
34 ms 49.233.29.122
1 2026-08-25 00:11 639232129927860324
2229 ms 49.233.29.122