DNS response history for ns2.yakken.net

ns2.yakken.net 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 31 DNS check records, 31 successful responses, 0 failed responses, and 386 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.yakken.net.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

386 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

133.18.239.148

Most recently resolved hosting IP on selected date

Successful Responses

31

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.yakken.net

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
31 2026-08-25 11:14 639232524938080723
523 ms 133.18.239.148
30 2026-08-25 10:21 639232492740373468
516 ms 133.18.239.148
29 2026-08-25 10:04 639232482235303141
511 ms 133.18.239.148
28 2026-08-25 09:46 639232471861770303
270 ms 133.18.239.148
27 2026-08-25 09:29 639232461630217327
256 ms 133.18.239.148
26 2026-08-25 09:12 639232451282965990
516 ms 133.18.239.148
25 2026-08-25 08:54 639232440814614938
257 ms 133.18.239.148
24 2026-08-25 08:37 639232430410720425
261 ms 133.18.239.148
23 2026-08-25 08:20 639232420003096185
260 ms 133.18.239.148
22 2026-08-25 08:02 639232409467287444
271 ms 133.18.239.148
21 2026-08-25 07:45 639232399077195997
513 ms 133.18.239.148
20 2026-08-25 07:27 639232388731528337
522 ms 133.18.239.148
19 2026-08-25 07:10 639232378288598612
267 ms 133.18.239.148
18 2026-08-25 06:16 639232346196373643
538 ms 133.18.239.148
17 2026-08-25 06:00 639232336112370741
282 ms 133.18.239.148
16 2026-08-25 05:43 639232326146508970
491 ms 133.18.239.148
15 2026-08-25 05:26 639232316189381720
8 ms 133.18.239.148
14 2026-08-25 05:10 639232306217998913
256 ms 133.18.239.148
13 2026-08-25 04:53 639232296255744174
515 ms 133.18.239.148
12 2026-08-25 04:36 639232286095760789
507 ms 133.18.239.148
11 2026-08-25 04:19 639232276086186273
277 ms 133.18.239.148
10 2026-08-25 04:03 639232265900986425
247 ms 133.18.239.148
9 2026-08-25 03:46 639232255723518075
529 ms 133.18.239.148
8 2026-08-25 03:29 639232245484452890
492 ms 133.18.239.148
7 2026-08-25 03:12 639232235157175331
532 ms 133.18.239.148
6 2026-08-25 02:18 639232203197189095
526 ms 133.18.239.148
5 2026-08-25 02:01 639232192844564298
267 ms 133.18.239.148
4 2026-08-25 01:44 639232182496008942
528 ms 133.18.239.148
3 2026-08-25 01:26 639232172197053132
493 ms 133.18.239.148
2 2026-08-25 00:33 639232140250307418
3 ms 133.18.239.148
1 2026-08-25 00:16 639232129927860324
532 ms 133.18.239.148