DNS response history for ns2.peppre.com

ns2.peppre.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 705 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.peppre.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

705 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

140.82.63.101

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.peppre.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:33 639232576780683689
2106 ms 140.82.63.101
35 2026-08-25 12:16 639232566381512620
191 ms 140.82.63.101
34 2026-08-25 11:59 639232556111768563
199 ms 140.82.63.101
33 2026-08-25 11:41 639232545839529039
101 ms 140.82.63.101
32 2026-08-25 11:24 639232535349285207
245 ms 140.82.63.101
31 2026-08-25 11:07 639232524938080723
198 ms 140.82.63.101
30 2026-08-25 10:13 639232492740373468
198 ms 140.82.63.101
29 2026-08-25 09:56 639232482235303141
2115 ms 140.82.63.101
28 2026-08-25 09:38 639232471861770303
20 ms 140.82.63.101
27 2026-08-25 09:21 639232461630217327
287 ms 140.82.63.101
26 2026-08-25 09:04 639232451282965990
201 ms 140.82.63.101
25 2026-08-25 08:46 639232440814614938
2011 ms 140.82.63.101
24 2026-08-25 08:29 639232430410720425
208 ms 140.82.63.101
23 2026-08-25 08:12 639232420003096185
231 ms 140.82.63.101
22 2026-08-25 07:54 639232409467287444
2104 ms 140.82.63.101
21 2026-08-25 07:37 639232399077195997
2016 ms 140.82.63.101
20 2026-08-25 07:20 639232388731528337
24 ms 140.82.63.101
19 2026-08-25 07:02 639232378288598612
7 ms 140.82.63.101
18 2026-08-25 06:09 639232346196373643
139 ms 140.82.63.101
17 2026-08-25 05:52 639232336112370741
6 ms 140.82.63.101
16 2026-08-25 05:35 639232326146508970
249 ms 140.82.63.101
15 2026-08-25 05:19 639232316189381720
191 ms 140.82.63.101
14 2026-08-25 05:02 639232306217998913
2046 ms 140.82.63.101
13 2026-08-25 04:46 639232296255744174
261 ms 140.82.63.101
12 2026-08-25 04:29 639232286095760789
2098 ms 140.82.63.101
11 2026-08-25 04:12 639232276086186273
2007 ms 140.82.63.101
10 2026-08-25 03:55 639232265900986425
101 ms 140.82.63.101
9 2026-08-25 03:38 639232255723518075
230 ms 140.82.63.101
8 2026-08-25 03:21 639232245484452890
246 ms 140.82.63.101
7 2026-08-25 03:04 639232235157175331
190 ms 140.82.63.101
6 2026-08-25 02:10 639232203197189095
2106 ms 140.82.63.101
5 2026-08-25 01:53 639232192844564298
208 ms 140.82.63.101
4 2026-08-25 01:36 639232182496008942
243 ms 140.82.63.101
3 2026-08-25 01:19 639232172197053132
266 ms 140.82.63.101
2 2026-08-25 00:25 639232140250307418
243 ms 140.82.63.101
1 2026-08-25 00:08 639232129927860324
2097 ms 140.82.63.101