DNS response history for ns2.yasex.link

ns2.yasex.link 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 35 DNS check records, 34 successful responses, 1 failed responses, and 93 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.yasex.link.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

93 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.23.145.118

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns2.yasex.link

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
35 2026-08-25 12:15 639232566381512620
121 ms 94.23.145.118
34 2026-08-25 11:58 639232556111768563
171 ms 94.23.145.118
33 2026-08-25 11:41 639232545839529039
148 ms 94.23.145.118
32 2026-08-25 11:23 639232535349285207
109 ms 94.23.145.118
31 2026-08-25 11:06 639232524938080723
130 ms 94.23.145.118
30 2026-08-25 10:12 639232492740373468
160 ms 94.23.145.118
29 2026-08-25 09:55 639232482235303141
79 ms 94.23.145.118
28 2026-08-25 09:37 639232471861770303
47 ms 94.23.145.118
27 2026-08-25 09:20 639232461630217327
153 ms 94.23.145.118
26 2026-08-25 09:03 639232451282965990
43 ms 94.23.145.118
25 2026-08-25 08:46 639232440814614938
64 ms 94.23.145.118
24 2026-08-25 08:28 639232430410720425
119 ms 94.23.145.118
23 2026-08-25 08:11 639232420003096185
83 ms 94.23.145.118
22 2026-08-25 07:53 639232409467287444
166 ms 94.23.145.118
21 2026-08-25 07:36 639232399077195997
125 ms 94.23.145.118
20 2026-08-25 07:19 639232388731528337
126 ms 94.23.145.118
19 2026-08-25 07:01 639232378288598612
77 ms 94.23.145.118
18 2026-08-25 06:08 639232346196373643
9 ms 94.23.145.118
17 2026-08-25 05:51 639232336112370741
44 ms 94.23.145.118
16 2026-08-25 05:34 639232326146508970
11 ms 94.23.145.118
15 2026-08-25 05:18 639232316189381720
110 ms 94.23.145.118
14 2026-08-25 05:01 639232306217998913
128 ms 94.23.145.118
13 2026-08-25 04:45 639232296255744174
105 ms 94.23.145.118
12 2026-08-25 04:28 639232286095760789
46 ms 94.23.145.118
11 2026-08-25 04:11 639232276086186273
66 ms 94.23.145.118
10 2026-08-25 03:54 639232265900986425
114 ms 94.23.145.118
9 2026-08-25 03:37 639232255723518075
47 ms 94.23.145.118
8 2026-08-25 03:20 639232245484452890
49 ms 94.23.145.118
7 2026-08-25 03:03 639232235157175331
56 ms 94.23.145.118
6 2026-08-25 02:09 639232203197189095
39 ms 94.23.145.118
5 2026-08-25 01:52 639232192844564298
-
4 2026-08-25 01:35 639232182496008942
68 ms 94.23.145.118
3 2026-08-25 01:18 639232172197053132
176 ms 94.23.145.118
2 2026-08-25 00:25 639232140250307418
151 ms 94.23.145.118
1 2026-08-25 00:07 639232129927860324
30 ms 94.23.145.118