DNS response history for ns2.philbystricanapps.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

253 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.219.248.201

Most recently resolved hosting IP on selected date

Successful Responses

37

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.philbystricanapps.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
37 2026-08-25 12:42 639232576780683689
307 ms 104.219.248.201
36 2026-08-25 12:25 639232566381512620
317 ms 104.219.248.201
35 2026-08-25 12:08 639232556111768563
305 ms 104.219.248.201
34 2026-08-25 11:51 639232545839529039
310 ms 104.219.248.201
33 2026-08-25 11:33 639232535349285207
298 ms 104.219.248.201
32 2026-08-25 11:16 639232524938080723
320 ms 104.219.248.201
31 2026-08-25 10:22 639232492740373468
146 ms 104.219.248.201
30 2026-08-25 10:05 639232482235303141
325 ms 104.219.248.201
29 2026-08-25 09:47 639232471861770303
152 ms 104.219.248.201
28 2026-08-25 09:30 639232461630217327
313 ms 104.219.248.201
27 2026-08-25 09:13 639232451282965990
174 ms 104.219.248.201
26 2026-08-25 08:56 639232440814614938
308 ms 104.219.248.201
25 2026-08-25 08:38 639232430410720425
317 ms 104.219.248.201
24 2026-08-25 08:21 639232420003096185
151 ms 104.219.248.201
23 2026-08-25 08:04 639232409467287444
153 ms 104.219.248.201
22 2026-08-25 07:46 639232399077195997
303 ms 104.219.248.201
21 2026-08-25 07:29 639232388731528337
329 ms 104.219.248.201
20 2026-08-25 07:12 639232378288598612
312 ms 104.219.248.201
19 2026-08-25 06:18 639232346196373643
309 ms 104.219.248.201
18 2026-08-25 06:01 639232336112370741
154 ms 104.219.248.201
17 2026-08-25 05:44 639232326146508970
293 ms 104.219.248.201
16 2026-08-25 05:28 639232316189381720
300 ms 104.219.248.201
15 2026-08-25 05:11 639232306217998913
151 ms 104.219.248.201
14 2026-08-25 04:54 639232296255744174
165 ms 104.219.248.201
13 2026-08-25 04:38 639232286095760789
320 ms 104.219.248.201
12 2026-08-25 04:21 639232276086186273
155 ms 104.219.248.201
11 2026-08-25 04:04 639232265900986425
165 ms 104.219.248.201
10 2026-08-25 03:47 639232255723518075
147 ms 104.219.248.201
9 2026-08-25 03:30 639232245484452890
328 ms 104.219.248.201
8 2026-08-25 03:13 639232235157175331
317 ms 104.219.248.201
7 2026-08-25 02:20 639232203197189095
301 ms 104.219.248.201
6 2026-08-25 02:03 639232192844564298
150 ms 104.219.248.201
5 2026-08-25 01:45 639232182496008942
323 ms 104.219.248.201
4 2026-08-25 01:28 639232172197053132
3 ms 104.219.248.201
3 2026-08-25 00:34 639232140250307418
308 ms 104.219.248.201
2 2026-08-25 00:18 639232129927860324
312 ms 104.219.248.201
1 2026-08-25 00:00 639232119551972438
319 ms 104.219.248.201