DNS response history for ns2.phimxxx.monster

ns2.phimxxx.monster 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 37 DNS check records, 36 successful responses, 1 failed responses, and 152 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.phimxxx.monster.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

152 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.68.36.101

Most recently resolved hosting IP on selected date

Successful Responses

36

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.phimxxx.monster

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
37 2026-08-25 12:51 639232587225721862
47 ms 51.68.36.101
36 2026-08-25 12:34 639232576780683689
59 ms 51.68.36.101
35 2026-08-25 12:16 639232566381512620
34 ms 51.68.36.101
34 2026-08-25 11:59 639232556111768563
49 ms 51.68.36.101
33 2026-08-25 11:42 639232545839529039
54 ms 51.68.36.101
32 2026-08-25 11:25 639232535349285207
-
31 2026-08-25 11:07 639232524938080723
49 ms 51.68.36.101
30 2026-08-25 10:13 639232492740373468
37 ms 51.68.36.101
29 2026-08-25 09:56 639232482235303141
28 ms 51.68.36.101
28 2026-08-25 09:39 639232471861770303
54 ms 51.68.36.101
27 2026-08-25 09:22 639232461630217327
45 ms 51.68.36.101
26 2026-08-25 09:05 639232451282965990
28 ms 51.68.36.101
25 2026-08-25 08:47 639232440814614938
23 ms 51.68.36.101
24 2026-08-25 08:30 639232430410720425
45 ms 51.68.36.101
23 2026-08-25 08:12 639232420003096185
39 ms 51.68.36.101
22 2026-08-25 07:55 639232409467287444
46 ms 51.68.36.101
21 2026-08-25 07:38 639232399077195997
7 ms 51.68.36.101
20 2026-08-25 07:20 639232388731528337
32 ms 51.68.36.101
19 2026-08-25 07:03 639232378288598612
40 ms 51.68.36.101
18 2026-08-25 06:09 639232346196373643
2030 ms 51.68.36.101
17 2026-08-25 05:53 639232336112370741
8 ms 51.68.36.101
16 2026-08-25 05:36 639232326146508970
2011 ms 51.68.36.101
15 2026-08-25 05:19 639232316189381720
52 ms 51.68.36.101
14 2026-08-25 05:03 639232306217998913
65 ms 51.68.36.101
13 2026-08-25 04:46 639232296255744174
9 ms 51.68.36.101
12 2026-08-25 04:29 639232286095760789
51 ms 51.68.36.101
11 2026-08-25 04:12 639232276086186273
51 ms 51.68.36.101
10 2026-08-25 03:56 639232265900986425
34 ms 51.68.36.101
9 2026-08-25 03:39 639232255723518075
35 ms 51.68.36.101
8 2026-08-25 03:22 639232245484452890
45 ms 51.68.36.101
7 2026-08-25 03:04 639232235157175331
35 ms 51.68.36.101
6 2026-08-25 02:11 639232203197189095
53 ms 51.68.36.101
5 2026-08-25 01:54 639232192844564298
46 ms 51.68.36.101
4 2026-08-25 01:37 639232182496008942
53 ms 51.68.36.101
3 2026-08-25 01:19 639232172197053132
73 ms 51.68.36.101
2 2026-08-25 00:26 639232140250307418
54 ms 51.68.36.101
1 2026-08-25 00:09 639232129927860324
43 ms 51.68.36.101