DNS response history for ns2.run415.com

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

39

Historical checks stored for this nameserver on selected date

Average Latency

285 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 13:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.175.14.122

Most recently resolved hosting IP on selected date

Successful Responses

39

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.run415.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
39 2026-08-26 13:03 639233455747096265
123 ms 69.175.14.122
38 2026-08-26 12:45 639233445367152284
121 ms 69.175.14.122
37 2026-08-26 12:28 639233434974187439
231 ms 69.175.14.122
36 2026-08-26 12:11 639233424567558554
225 ms 69.175.14.122
35 2026-08-26 11:53 639233414056832719
232 ms 69.175.14.122
34 2026-08-26 11:36 639233403515141099
2119 ms 69.175.14.122
33 2026-08-26 10:41 639233370841350248
230 ms 69.175.14.122
32 2026-08-26 10:24 639233360361507238
225 ms 69.175.14.122
31 2026-08-26 10:06 639233350067824371
117 ms 69.175.14.122
30 2026-08-26 09:49 639233339545274518
116 ms 69.175.14.122
29 2026-08-26 09:32 639233329214918079
117 ms 69.175.14.122
28 2026-08-26 09:14 639233318749762337
225 ms 69.175.14.122
27 2026-08-26 08:57 639233308387917838
111 ms 69.175.14.122
26 2026-08-26 08:40 639233297961740122
115 ms 69.175.14.122
25 2026-08-26 08:22 639233287487159094
225 ms 69.175.14.122
24 2026-08-26 08:05 639233276995531707
221 ms 69.175.14.122
23 2026-08-26 07:47 639233266521568229
243 ms 69.175.14.122
22 2026-08-26 07:30 639233256081047431
226 ms 69.175.14.122
21 2026-08-26 06:36 639233223620132921
225 ms 69.175.14.122
20 2026-08-26 06:19 639233213287814244
228 ms 69.175.14.122
19 2026-08-26 06:01 639233202925983161
113 ms 69.175.14.122
18 2026-08-26 05:44 639233192644780696
223 ms 69.175.14.122
17 2026-08-26 05:27 639233182401183833
227 ms 69.175.14.122
16 2026-08-26 05:10 639233172074181051
122 ms 69.175.14.122
15 2026-08-26 04:53 639233161808421455
228 ms 69.175.14.122
14 2026-08-26 04:36 639233151357344052
223 ms 69.175.14.122
13 2026-08-26 04:18 639233141034116946
110 ms 69.175.14.122
12 2026-08-26 04:01 639233130828334142
227 ms 69.175.14.122
11 2026-08-26 03:44 639233120373450007
223 ms 69.175.14.122
10 2026-08-26 03:26 639233110066216193
112 ms 69.175.14.122
9 2026-08-26 02:33 639233078065410564
110 ms 69.175.14.122
8 2026-08-26 02:16 639233067787457832
220 ms 69.175.14.122
7 2026-08-26 01:59 639233057501801162
234 ms 69.175.14.122
6 2026-08-26 01:42 639233047089431703
124 ms 69.175.14.122
5 2026-08-26 01:24 639233036754790688
2136 ms 69.175.14.122
4 2026-08-26 01:07 639233026412602472
240 ms 69.175.14.122
3 2026-08-26 00:50 639233016064066127
217 ms 69.175.14.122
2 2026-08-26 00:33 639233005922655772
222 ms 69.175.14.122
1 2026-08-26 00:16 639232995672256907
111 ms 69.175.14.122