DNS response history for dns2.prodigperu.com

dns2.prodigperu.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 240 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 dns2.prodigperu.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

240 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.31.176.180

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 dns2.prodigperu.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:36 639232576780683689
245 ms 50.31.176.180
35 2026-08-25 12:19 639232566381512620
127 ms 50.31.176.180
34 2026-08-25 12:01 639232556111768563
118 ms 50.31.176.180
33 2026-08-25 11:44 639232545839529039
125 ms 50.31.176.180
32 2026-08-25 11:27 639232535349285207
2008 ms 50.31.176.180
31 2026-08-25 11:09 639232524938080723
141 ms 50.31.176.180
30 2026-08-25 10:16 639232492740373468
244 ms 50.31.176.180
29 2026-08-25 09:59 639232482235303141
112 ms 50.31.176.180
28 2026-08-25 09:41 639232471861770303
118 ms 50.31.176.180
27 2026-08-25 09:24 639232461630217327
121 ms 50.31.176.180
26 2026-08-25 09:07 639232451282965990
116 ms 50.31.176.180
25 2026-08-25 08:49 639232440814614938
127 ms 50.31.176.180
24 2026-08-25 08:32 639232430410720425
118 ms 50.31.176.180
23 2026-08-25 08:15 639232420003096185
119 ms 50.31.176.180
22 2026-08-25 07:57 639232409467287444
119 ms 50.31.176.180
21 2026-08-25 07:40 639232399077195997
117 ms 50.31.176.180
20 2026-08-25 07:22 639232388731528337
242 ms 50.31.176.180
19 2026-08-25 07:05 639232378288598612
234 ms 50.31.176.180
18 2026-08-25 06:12 639232346196373643
118 ms 50.31.176.180
17 2026-08-25 05:55 639232336112370741
112 ms 50.31.176.180
16 2026-08-25 05:38 639232326146508970
115 ms 50.31.176.180
15 2026-08-25 05:21 639232316189381720
9 ms 50.31.176.180
14 2026-08-25 05:05 639232306217998913
2141 ms 50.31.176.180
13 2026-08-25 04:48 639232296255744174
7 ms 50.31.176.180
12 2026-08-25 04:31 639232286095760789
114 ms 50.31.176.180
11 2026-08-25 04:15 639232276086186273
126 ms 50.31.176.180
10 2026-08-25 03:58 639232265900986425
116 ms 50.31.176.180
9 2026-08-25 03:41 639232255723518075
116 ms 50.31.176.180
8 2026-08-25 03:24 639232245484452890
33 ms 50.31.176.180
7 2026-08-25 03:07 639232235157175331
235 ms 50.31.176.180
6 2026-08-25 02:13 639232203197189095
237 ms 50.31.176.180
5 2026-08-25 01:56 639232192844564298
125 ms 50.31.176.180
4 2026-08-25 01:39 639232182496008942
127 ms 50.31.176.180
3 2026-08-25 01:22 639232172197053132
123 ms 50.31.176.180
2 2026-08-25 00:28 639232140250307418
120 ms 50.31.176.180
1 2026-08-25 00:11 639232129927860324
130 ms 50.31.176.180