DNS response history for ns2.poopyfeed.net

ns2.poopyfeed.net 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 432 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.poopyfeed.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

432 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

204.111.10.5

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.poopyfeed.net

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:03 639232556111768563
257 ms 204.111.10.5
33 2026-08-25 11:46 639232545839529039
258 ms 204.111.10.5
32 2026-08-25 11:28 639232535349285207
176 ms 204.111.10.5
31 2026-08-25 11:11 639232524938080723
255 ms 204.111.10.5
30 2026-08-25 10:17 639232492740373468
253 ms 204.111.10.5
29 2026-08-25 10:00 639232482235303141
260 ms 204.111.10.5
28 2026-08-25 09:42 639232471861770303
252 ms 204.111.10.5
27 2026-08-25 09:25 639232461630217327
249 ms 204.111.10.5
26 2026-08-25 09:08 639232451282965990
253 ms 204.111.10.5
25 2026-08-25 08:51 639232440814614938
161 ms 204.111.10.5
24 2026-08-25 08:33 639232430410720425
253 ms 204.111.10.5
23 2026-08-25 08:16 639232420003096185
4 ms 204.111.10.5
22 2026-08-25 07:59 639232409467287444
2160 ms 204.111.10.5
21 2026-08-25 07:41 639232399077195997
4 ms 204.111.10.5
20 2026-08-25 07:24 639232388731528337
268 ms 204.111.10.5
19 2026-08-25 07:06 639232378288598612
256 ms 204.111.10.5
18 2026-08-25 06:13 639232346196373643
258 ms 204.111.10.5
17 2026-08-25 05:56 639232336112370741
258 ms 204.111.10.5
16 2026-08-25 05:39 639232326146508970
4 ms 204.111.10.5
15 2026-08-25 05:23 639232316189381720
2 ms 204.111.10.5
14 2026-08-25 05:06 639232306217998913
253 ms 204.111.10.5
13 2026-08-25 04:50 639232296255744174
248 ms 204.111.10.5
12 2026-08-25 04:33 639232286095760789
264 ms 204.111.10.5
11 2026-08-25 04:16 639232276086186273
259 ms 204.111.10.5
10 2026-08-25 03:59 639232265900986425
2109 ms 204.111.10.5
9 2026-08-25 03:42 639232255723518075
250 ms 204.111.10.5
8 2026-08-25 03:25 639232245484452890
251 ms 204.111.10.5
7 2026-08-25 03:08 639232235157175331
251 ms 204.111.10.5
6 2026-08-25 02:15 639232203197189095
274 ms 204.111.10.5
5 2026-08-25 01:58 639232192844564298
4111 ms 204.111.10.5
4 2026-08-25 01:40 639232182496008942
148 ms 204.111.10.5
3 2026-08-25 01:23 639232172197053132
247 ms 204.111.10.5
2 2026-08-25 00:30 639232140250307418
4 ms 204.111.10.5
1 2026-08-25 00:13 639232129927860324
172 ms 204.111.10.5