DNS response history for iperform.app

iperform.app 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, 36 successful responses, 1 failed responses, and 304 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 iperform.app.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

304 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

86.121.255.192

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for iperform.app

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:25 639233434974187439
98 ms 86.121.255.192
36 2026-08-26 12:07 639233424567558554
102 ms 86.121.255.192
35 2026-08-26 11:50 639233414056832719
64 ms 86.121.255.192
34 2026-08-26 11:32 639233403515141099
94 ms 86.121.255.192
33 2026-08-26 10:38 639233370841350248
2066 ms 86.121.255.192
32 2026-08-26 10:20 639233360361507238
64 ms 86.121.255.192
31 2026-08-26 10:03 639233350067824371
64 ms 86.121.255.192
30 2026-08-26 09:46 639233339545274518
104 ms 86.121.255.192
29 2026-08-26 09:28 639233329214918079
80 ms 86.121.255.192
28 2026-08-26 09:11 639233318749762337
86 ms 86.121.255.192
27 2026-08-26 08:54 639233308387917838
61 ms 86.121.255.192
26 2026-08-26 08:36 639233297961740122
85 ms 86.121.255.192
25 2026-08-26 08:19 639233287487159094
58 ms 86.121.255.192
24 2026-08-26 08:01 639233276995531707
77 ms 86.121.255.192
23 2026-08-26 07:44 639233266521568229
92 ms 86.121.255.192
22 2026-08-26 07:26 639233256081047431
75 ms 86.121.255.192
21 2026-08-26 06:33 639233223620132921
84 ms 86.121.255.192
20 2026-08-26 06:15 639233213287814244
101 ms 86.121.255.192
19 2026-08-26 05:58 639233202925983161
89 ms 86.121.255.192
18 2026-08-26 05:41 639233192644780696
151 ms 86.121.255.192
17 2026-08-26 05:24 639233182401183833
87 ms 86.121.255.192
16 2026-08-26 05:07 639233172074181051
13 ms 86.121.255.192
15 2026-08-26 04:49 639233161808421455
-
14 2026-08-26 04:32 639233151357344052
54 ms 86.121.255.192
13 2026-08-26 04:15 639233141034116946
88 ms 86.121.255.192
12 2026-08-26 03:58 639233130828334142
133 ms 86.121.255.192
11 2026-08-26 03:40 639233120373450007
53 ms 86.121.255.192
10 2026-08-26 03:23 639233110066216193
114 ms 86.121.255.192
9 2026-08-26 02:30 639233078065410564
87 ms 86.121.255.192
8 2026-08-26 02:13 639233067787457832
136 ms 86.121.255.192
7 2026-08-26 01:56 639233057501801162
16 ms 86.121.255.192
6 2026-08-26 01:38 639233047089431703
2076 ms 86.121.255.192
5 2026-08-26 01:21 639233036754790688
96 ms 86.121.255.192
4 2026-08-26 01:04 639233026412602472
59 ms 86.121.255.192
3 2026-08-26 00:46 639233016064066127
2076 ms 86.121.255.192
2 2026-08-26 00:29 639233005922655772
87 ms 86.121.255.192
1 2026-08-26 00:13 639232995672256907
2067 ms 86.121.255.192