DNS response history for ns2.phr.com.ph

ns2.phr.com.ph 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 35 DNS check records, 35 successful responses, 0 failed responses, and 407 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.phr.com.ph.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

407 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.105.174.142

Most recently resolved hosting IP on selected date

Successful Responses

35

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.phr.com.ph

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
35 2026-08-25 12:24 639232566381512620
617 ms 172.105.174.142
34 2026-08-25 12:06 639232556111768563
599 ms 172.105.174.142
33 2026-08-25 11:49 639232545839529039
5 ms 172.105.174.142
32 2026-08-25 11:32 639232535349285207
307 ms 172.105.174.142
31 2026-08-25 11:14 639232524938080723
5 ms 172.105.174.142
30 2026-08-25 10:21 639232492740373468
636 ms 172.105.174.142
29 2026-08-25 10:04 639232482235303141
4 ms 172.105.174.142
28 2026-08-25 09:46 639232471861770303
9 ms 172.105.174.142
27 2026-08-25 09:29 639232461630217327
304 ms 172.105.174.142
26 2026-08-25 09:12 639232451282965990
309 ms 172.105.174.142
25 2026-08-25 08:54 639232440814614938
605 ms 172.105.174.142
24 2026-08-25 08:37 639232430410720425
299 ms 172.105.174.142
23 2026-08-25 08:20 639232420003096185
313 ms 172.105.174.142
22 2026-08-25 08:02 639232409467287444
606 ms 172.105.174.142
21 2026-08-25 07:45 639232399077195997
308 ms 172.105.174.142
20 2026-08-25 07:27 639232388731528337
608 ms 172.105.174.142
19 2026-08-25 07:10 639232378288598612
635 ms 172.105.174.142
18 2026-08-25 06:16 639232346196373643
10 ms 172.105.174.142
17 2026-08-25 06:00 639232336112370741
311 ms 172.105.174.142
16 2026-08-25 05:43 639232326146508970
4 ms 172.105.174.142
15 2026-08-25 05:26 639232316189381720
300 ms 172.105.174.142
14 2026-08-25 05:10 639232306217998913
3 ms 172.105.174.142
13 2026-08-25 04:53 639232296255744174
3 ms 172.105.174.142
12 2026-08-25 04:36 639232286095760789
303 ms 172.105.174.142
11 2026-08-25 04:19 639232276086186273
311 ms 172.105.174.142
10 2026-08-25 04:03 639232265900986425
601 ms 172.105.174.142
9 2026-08-25 03:46 639232255723518075
308 ms 172.105.174.142
8 2026-08-25 03:29 639232245484452890
600 ms 172.105.174.142
7 2026-08-25 03:12 639232235157175331
601 ms 172.105.174.142
6 2026-08-25 02:18 639232203197189095
302 ms 172.105.174.142
5 2026-08-25 02:01 639232192844564298
305 ms 172.105.174.142
4 2026-08-25 01:44 639232182496008942
623 ms 172.105.174.142
3 2026-08-25 01:26 639232172197053132
608 ms 172.105.174.142
2 2026-08-25 00:33 639232140250307418
2286 ms 172.105.174.142
1 2026-08-25 00:16 639232129927860324
599 ms 172.105.174.142