DNS response history for ns2.dnspepper.com

ns2.dnspepper.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-26. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 220 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.dnspepper.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

220 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

167.150.89.6

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.dnspepper.com

Showing DNS history for 2026-08-26 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-26 12:29 639233434974187439
150 ms 167.150.89.6
36 2026-08-26 12:11 639233424567558554
302 ms 167.150.89.6
35 2026-08-26 11:54 639233414056832719
159 ms 167.150.89.6
34 2026-08-26 11:37 639233403515141099
298 ms 167.150.89.6
33 2026-08-26 10:42 639233370841350248
318 ms 167.150.89.6
32 2026-08-26 10:25 639233360361507238
303 ms 167.150.89.6
31 2026-08-26 10:07 639233350067824371
307 ms 167.150.89.6
30 2026-08-26 09:50 639233339545274518
173 ms 167.150.89.6
29 2026-08-26 09:32 639233329214918079
310 ms 167.150.89.6
28 2026-08-26 09:15 639233318749762337
262 ms 167.150.89.6
27 2026-08-26 08:58 639233308387917838
308 ms 167.150.89.6
26 2026-08-26 08:41 639233297961740122
160 ms 167.150.89.6
25 2026-08-26 08:23 639233287487159094
312 ms 167.150.89.6
24 2026-08-26 08:06 639233276995531707
148 ms 167.150.89.6
23 2026-08-26 07:48 639233266521568229
297 ms 167.150.89.6
22 2026-08-26 07:31 639233256081047431
207 ms 167.150.89.6
21 2026-08-26 06:37 639233223620132921
319 ms 167.150.89.6
20 2026-08-26 06:19 639233213287814244
157 ms 167.150.89.6
19 2026-08-26 06:02 639233202925983161
298 ms 167.150.89.6
18 2026-08-26 05:45 639233192644780696
151 ms 167.150.89.6
17 2026-08-26 05:28 639233182401183833
155 ms 167.150.89.6
16 2026-08-26 05:11 639233172074181051
148 ms 167.150.89.6
15 2026-08-26 04:53 639233161808421455
153 ms 167.150.89.6
14 2026-08-26 04:36 639233151357344052
148 ms 167.150.89.6
13 2026-08-26 04:19 639233141034116946
149 ms 167.150.89.6
12 2026-08-26 04:02 639233130828334142
159 ms 167.150.89.6
11 2026-08-26 03:45 639233120373450007
148 ms 167.150.89.6
10 2026-08-26 03:27 639233110066216193
148 ms 167.150.89.6
9 2026-08-26 02:34 639233078065410564
299 ms 167.150.89.6
8 2026-08-26 02:17 639233067787457832
297 ms 167.150.89.6
7 2026-08-26 02:00 639233057501801162
150 ms 167.150.89.6
6 2026-08-26 01:43 639233047089431703
150 ms 167.150.89.6
5 2026-08-26 01:25 639233036754790688
158 ms 167.150.89.6
4 2026-08-26 01:08 639233026412602472
149 ms 167.150.89.6
3 2026-08-26 00:51 639233016064066127
298 ms 167.150.89.6
2 2026-08-26 00:34 639233005922655772
203 ms 167.150.89.6
1 2026-08-26 00:17 639232995672256907
296 ms 167.150.89.6