DNS response history for ns2.yanki.in

ns2.yanki.in 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 290 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.yanki.in.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

290 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.160.145.70

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.yanki.in

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:13 639232524938080723
2 ms 103.160.145.70
30 2026-08-25 10:20 639232492740373468
271 ms 103.160.145.70
29 2026-08-25 10:03 639232482235303141
267 ms 103.160.145.70
28 2026-08-25 09:45 639232471861770303
271 ms 103.160.145.70
27 2026-08-25 09:28 639232461630217327
278 ms 103.160.145.70
26 2026-08-25 09:11 639232451282965990
3 ms 103.160.145.70
25 2026-08-25 08:53 639232440814614938
283 ms 103.160.145.70
24 2026-08-25 08:36 639232430410720425
267 ms 103.160.145.70
23 2026-08-25 08:19 639232420003096185
4 ms 103.160.145.70
22 2026-08-25 08:01 639232409467287444
130 ms 103.160.145.70
21 2026-08-25 07:44 639232399077195997
4 ms 103.160.145.70
20 2026-08-25 07:26 639232388731528337
269 ms 103.160.145.70
19 2026-08-25 07:09 639232378288598612
272 ms 103.160.145.70
18 2026-08-25 06:15 639232346196373643
388 ms 103.160.145.70
17 2026-08-25 05:59 639232336112370741
4 ms 103.160.145.70
16 2026-08-25 05:42 639232326146508970
134 ms 103.160.145.70
15 2026-08-25 05:25 639232316189381720
277 ms 103.160.145.70
14 2026-08-25 05:09 639232306217998913
270 ms 103.160.145.70
13 2026-08-25 04:52 639232296255744174
276 ms 103.160.145.70
12 2026-08-25 04:35 639232286095760789
267 ms 103.160.145.70
11 2026-08-25 04:18 639232276086186273
277 ms 103.160.145.70
10 2026-08-25 04:02 639232265900986425
282 ms 103.160.145.70
9 2026-08-25 03:45 639232255723518075
299 ms 103.160.145.70
8 2026-08-25 03:28 639232245484452890
293 ms 103.160.145.70
7 2026-08-25 03:10 639232235157175331
269 ms 103.160.145.70
6 2026-08-25 02:17 639232203197189095
259 ms 103.160.145.70
5 2026-08-25 02:00 639232192844564298
316 ms 103.160.145.70
4 2026-08-25 01:43 639232182496008942
2224 ms 103.160.145.70
3 2026-08-25 01:26 639232172197053132
279 ms 103.160.145.70
2 2026-08-25 00:32 639232140250307418
268 ms 103.160.145.70
1 2026-08-25 00:15 639232129927860324
280 ms 103.160.145.70