DNS response history for ns1.drtrendperu.com

ns1.drtrendperu.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 34 DNS check records, 34 successful responses, 0 failed responses, and 386 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 ns1.drtrendperu.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

386 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

161.132.51.205

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 ns1.drtrendperu.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
34 2026-08-26 10:44 639233370841350248
179 ms 161.132.51.205
33 2026-08-26 10:27 639233360361507238
376 ms 161.132.51.205
32 2026-08-26 10:09 639233350067824371
373 ms 161.132.51.205
31 2026-08-26 09:52 639233339545274518
358 ms 161.132.51.205
30 2026-08-26 09:34 639233329214918079
378 ms 161.132.51.205
29 2026-08-26 09:17 639233318749762337
357 ms 161.132.51.205
28 2026-08-26 09:00 639233308387917838
180 ms 161.132.51.205
27 2026-08-26 08:42 639233297961740122
371 ms 161.132.51.205
26 2026-08-26 08:25 639233287487159094
364 ms 161.132.51.205
25 2026-08-26 08:08 639233276995531707
373 ms 161.132.51.205
24 2026-08-26 07:50 639233266521568229
359 ms 161.132.51.205
23 2026-08-26 07:32 639233256081047431
359 ms 161.132.51.205
22 2026-08-26 06:39 639233223620132921
2178 ms 161.132.51.205
21 2026-08-26 06:21 639233213287814244
356 ms 161.132.51.205
20 2026-08-26 06:04 639233202925983161
357 ms 161.132.51.205
19 2026-08-26 05:47 639233192644780696
372 ms 161.132.51.205
18 2026-08-26 05:30 639233182401183833
379 ms 161.132.51.205
17 2026-08-26 05:13 639233172074181051
288 ms 161.132.51.205
16 2026-08-26 04:55 639233161808421455
358 ms 161.132.51.205
15 2026-08-26 04:38 639233151357344052
357 ms 161.132.51.205
14 2026-08-26 04:21 639233141034116946
368 ms 161.132.51.205
13 2026-08-26 04:04 639233130828334142
10 ms 161.132.51.205
12 2026-08-26 03:46 639233120373450007
356 ms 161.132.51.205
11 2026-08-26 03:29 639233110066216193
367 ms 161.132.51.205
10 2026-08-26 02:36 639233078065410564
355 ms 161.132.51.205
9 2026-08-26 02:19 639233067787457832
356 ms 161.132.51.205
8 2026-08-26 02:02 639233057501801162
383 ms 161.132.51.205
7 2026-08-26 01:44 639233047089431703
179 ms 161.132.51.205
6 2026-08-26 01:27 639233036754790688
366 ms 161.132.51.205
5 2026-08-26 01:10 639233026412602472
371 ms 161.132.51.205
4 2026-08-26 00:53 639233016064066127
379 ms 161.132.51.205
3 2026-08-26 00:35 639233005922655772
359 ms 161.132.51.205
2 2026-08-26 00:18 639232995672256907
227 ms 161.132.51.205
1 2026-08-26 00:01 639232985300872416
371 ms 161.132.51.205