DNS response history for ns2.phoebepatient.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

318 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

97.64.233.66

Most recently resolved hosting IP on selected date

Successful Responses

36

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.phoebepatient.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
36 2026-08-25 12:39 639232576780683689
217 ms 97.64.233.66
35 2026-08-25 12:22 639232566381512620
217 ms 97.64.233.66
34 2026-08-25 12:04 639232556111768563
172 ms 97.64.233.66
33 2026-08-25 11:47 639232545839529039
116 ms 97.64.233.66
32 2026-08-25 11:30 639232535349285207
211 ms 97.64.233.66
31 2026-08-25 11:13 639232524938080723
263 ms 97.64.233.66
30 2026-08-25 10:19 639232492740373468
207 ms 97.64.233.66
29 2026-08-25 10:02 639232482235303141
275 ms 97.64.233.66
28 2026-08-25 09:44 639232471861770303
218 ms 97.64.233.66
27 2026-08-25 09:27 639232461630217327
240 ms 97.64.233.66
26 2026-08-25 09:10 639232451282965990
116 ms 97.64.233.66
25 2026-08-25 08:52 639232440814614938
232 ms 97.64.233.66
24 2026-08-25 08:35 639232430410720425
213 ms 97.64.233.66
23 2026-08-25 08:18 639232420003096185
231 ms 97.64.233.66
22 2026-08-25 08:00 639232409467287444
214 ms 97.64.233.66
21 2026-08-25 07:43 639232399077195997
229 ms 97.64.233.66
20 2026-08-25 07:26 639232388731528337
2119 ms 97.64.233.66
19 2026-08-25 07:08 639232378288598612
228 ms 97.64.233.66
18 2026-08-25 06:15 639232346196373643
226 ms 97.64.233.66
17 2026-08-25 05:58 639232336112370741
118 ms 97.64.233.66
16 2026-08-25 05:41 639232326146508970
228 ms 97.64.233.66
15 2026-08-25 05:24 639232316189381720
457 ms 97.64.233.66
14 2026-08-25 05:08 639232306217998913
214 ms 97.64.233.66
13 2026-08-25 04:51 639232296255744174
214 ms 97.64.233.66
12 2026-08-25 04:34 639232286095760789
114 ms 97.64.233.66
11 2026-08-25 04:17 639232276086186273
143 ms 97.64.233.66
10 2026-08-25 04:01 639232265900986425
211 ms 97.64.233.66
9 2026-08-25 03:44 639232255723518075
113 ms 97.64.233.66
8 2026-08-25 03:27 639232245484452890
114 ms 97.64.233.66
7 2026-08-25 03:10 639232235157175331
225 ms 97.64.233.66
6 2026-08-25 02:16 639232203197189095
2213 ms 97.64.233.66
5 2026-08-25 01:59 639232192844564298
257 ms 97.64.233.66
4 2026-08-25 01:42 639232182496008942
209 ms 97.64.233.66
3 2026-08-25 01:25 639232172197053132
219 ms 97.64.233.66
2 2026-08-25 00:31 639232140250307418
208 ms 97.64.233.66
1 2026-08-25 00:14 639232129927860324
229 ms 97.64.233.66