DNS response history for ns2.runwp.run

ns2.runwp.run 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 355 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.runwp.run.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

355 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

15.197.172.60

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 ns2.runwp.run

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:43 639233370841350248
111 ms 15.197.172.60
33 2026-08-26 10:26 639233360361507238
380 ms 15.197.172.60
32 2026-08-26 10:08 639233350067824371
649 ms 15.197.172.60
31 2026-08-26 09:51 639233339545274518
354 ms 15.197.172.60
30 2026-08-26 09:34 639233329214918079
585 ms 15.197.172.60
29 2026-08-26 09:16 639233318749762337
139 ms 15.197.172.60
28 2026-08-26 08:59 639233308387917838
2138 ms 15.197.172.60
27 2026-08-26 08:42 639233297961740122
234 ms 15.197.172.60
26 2026-08-26 08:24 639233287487159094
612 ms 15.197.172.60
25 2026-08-26 08:07 639233276995531707
119 ms 15.197.172.60
24 2026-08-26 07:49 639233266521568229
136 ms 15.197.172.60
23 2026-08-26 07:32 639233256081047431
265 ms 15.197.172.60
22 2026-08-26 06:38 639233223620132921
292 ms 15.197.172.60
21 2026-08-26 06:21 639233213287814244
109 ms 15.197.172.60
20 2026-08-26 06:03 639233202925983161
254 ms 15.197.172.60
19 2026-08-26 05:46 639233192644780696
196 ms 15.197.172.60
18 2026-08-26 05:29 639233182401183833
116 ms 15.197.172.60
17 2026-08-26 05:12 639233172074181051
388 ms 15.197.172.60
16 2026-08-26 04:55 639233161808421455
265 ms 15.197.172.60
15 2026-08-26 04:38 639233151357344052
270 ms 15.197.172.60
14 2026-08-26 04:20 639233141034116946
386 ms 15.197.172.60
13 2026-08-26 04:03 639233130828334142
245 ms 15.197.172.60
12 2026-08-26 03:46 639233120373450007
260 ms 15.197.172.60
11 2026-08-26 03:28 639233110066216193
260 ms 15.197.172.60
10 2026-08-26 02:35 639233078065410564
384 ms 15.197.172.60
9 2026-08-26 02:18 639233067787457832
358 ms 15.197.172.60
8 2026-08-26 02:01 639233057501801162
372 ms 15.197.172.60
7 2026-08-26 01:44 639233047089431703
259 ms 15.197.172.60
6 2026-08-26 01:26 639233036754790688
494 ms 15.197.172.60
5 2026-08-26 01:09 639233026412602472
383 ms 15.197.172.60
4 2026-08-26 00:52 639233016064066127
128 ms 15.197.172.60
3 2026-08-26 00:35 639233005922655772
262 ms 15.197.172.60
2 2026-08-26 00:18 639232995672256907
385 ms 15.197.172.60
1 2026-08-26 00:01 639232985300872416
282 ms 15.197.172.60