DNS response history for ns2.peeragefashion.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

311 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.62.85.23

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.peeragefashion.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
36 2026-08-26 12:11 639233424567558554
666 ms 69.62.85.23
35 2026-08-26 11:53 639233414056832719
146 ms 69.62.85.23
34 2026-08-26 11:36 639233403515141099
376 ms 69.62.85.23
33 2026-08-26 10:41 639233370841350248
376 ms 69.62.85.23
32 2026-08-26 10:24 639233360361507238
181 ms 69.62.85.23
31 2026-08-26 10:07 639233350067824371
673 ms 69.62.85.23
30 2026-08-26 09:50 639233339545274518
535 ms 69.62.85.23
29 2026-08-26 09:32 639233329214918079
7 ms 69.62.85.23
28 2026-08-26 09:15 639233318749762337
16 ms 69.62.85.23
27 2026-08-26 08:57 639233308387917838
419 ms 69.62.85.23
26 2026-08-26 08:40 639233297961740122
626 ms 69.62.85.23
25 2026-08-26 08:23 639233287487159094
140 ms 69.62.85.23
24 2026-08-26 08:05 639233276995531707
202 ms 69.62.85.23
23 2026-08-26 07:47 639233266521568229
12 ms 69.62.85.23
22 2026-08-26 07:30 639233256081047431
9 ms 69.62.85.23
21 2026-08-26 06:36 639233223620132921
224 ms 69.62.85.23
20 2026-08-26 06:19 639233213287814244
534 ms 69.62.85.23
19 2026-08-26 06:01 639233202925983161
3 ms 69.62.85.23
18 2026-08-26 05:44 639233192644780696
4 ms 69.62.85.23
17 2026-08-26 05:27 639233182401183833
279 ms 69.62.85.23
16 2026-08-26 05:10 639233172074181051
284 ms 69.62.85.23
15 2026-08-26 04:53 639233161808421455
292 ms 69.62.85.23
14 2026-08-26 04:36 639233151357344052
396 ms 69.62.85.23
13 2026-08-26 04:18 639233141034116946
2134 ms 69.62.85.23
12 2026-08-26 04:01 639233130828334142
267 ms 69.62.85.23
11 2026-08-26 03:44 639233120373450007
128 ms 69.62.85.23
10 2026-08-26 03:27 639233110066216193
150 ms 69.62.85.23
9 2026-08-26 02:33 639233078065410564
272 ms 69.62.85.23
8 2026-08-26 02:16 639233067787457832
187 ms 69.62.85.23
7 2026-08-26 01:59 639233057501801162
278 ms 69.62.85.23
6 2026-08-26 01:42 639233047089431703
395 ms 69.62.85.23
5 2026-08-26 01:25 639233036754790688
152 ms 69.62.85.23
4 2026-08-26 01:07 639233026412602472
282 ms 69.62.85.23
3 2026-08-26 00:50 639233016064066127
273 ms 69.62.85.23
2 2026-08-26 00:33 639233005922655772
137 ms 69.62.85.23
1 2026-08-26 00:16 639232995672256907
158 ms 69.62.85.23