DNS response history for ns2.yasexe.pro

ns2.yasexe.pro 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-25. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 181 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.yasexe.pro.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

181 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

135.125.65.216

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.yasexe.pro

Showing DNS history for 2026-08-25 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-25 12:31 639232576780683689
40 ms 135.125.65.216
35 2026-08-25 12:13 639232566381512620
63 ms 135.125.65.216
34 2026-08-25 11:56 639232556111768563
2053 ms 135.125.65.216
33 2026-08-25 11:39 639232545839529039
170 ms 135.125.65.216
32 2026-08-25 11:22 639232535349285207
72 ms 135.125.65.216
31 2026-08-25 11:04 639232524938080723
51 ms 135.125.65.216
30 2026-08-25 10:11 639232492740373468
191 ms 135.125.65.216
29 2026-08-25 09:53 639232482235303141
54 ms 135.125.65.216
28 2026-08-25 09:36 639232471861770303
24 ms 135.125.65.216
27 2026-08-25 09:19 639232461630217327
42 ms 135.125.65.216
26 2026-08-25 09:01 639232451282965990
45 ms 135.125.65.216
25 2026-08-25 08:44 639232440814614938
19 ms 135.125.65.216
24 2026-08-25 08:27 639232430410720425
504 ms 135.125.65.216
23 2026-08-25 08:09 639232420003096185
55 ms 135.125.65.216
22 2026-08-25 07:52 639232409467287444
40 ms 135.125.65.216
21 2026-08-25 07:35 639232399077195997
50 ms 135.125.65.216
20 2026-08-25 07:17 639232388731528337
45 ms 135.125.65.216
19 2026-08-25 07:00 639232378288598612
44 ms 135.125.65.216
18 2026-08-25 06:06 639232346196373643
184 ms 135.125.65.216
17 2026-08-25 05:50 639232336112370741
2080 ms 135.125.65.216
16 2026-08-25 05:33 639232326146508970
79 ms 135.125.65.216
15 2026-08-25 05:16 639232316189381720
34 ms 135.125.65.216
14 2026-08-25 05:00 639232306217998913
24 ms 135.125.65.216
13 2026-08-25 04:43 639232296255744174
65 ms 135.125.65.216
12 2026-08-25 04:26 639232286095760789
25 ms 135.125.65.216
11 2026-08-25 04:09 639232276086186273
16 ms 135.125.65.216
10 2026-08-25 03:53 639232265900986425
57 ms 135.125.65.216
9 2026-08-25 03:36 639232255723518075
19 ms 135.125.65.216
8 2026-08-25 03:19 639232245484452890
46 ms 135.125.65.216
7 2026-08-25 03:01 639232235157175331
49 ms 135.125.65.216
6 2026-08-25 02:08 639232203197189095
41 ms 135.125.65.216
5 2026-08-25 01:51 639232192844564298
4 ms 135.125.65.216
4 2026-08-25 01:34 639232182496008942
44 ms 135.125.65.216
3 2026-08-25 01:16 639232172197053132
64 ms 135.125.65.216
2 2026-08-25 00:23 639232140250307418
64 ms 135.125.65.216
1 2026-08-25 00:06 639232129927860324
56 ms 135.125.65.216