DNS response history for ns2.yabistar.com

ns2.yabistar.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-25. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 472 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.yabistar.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

472 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.216.180.60

Most recently resolved hosting IP on selected date

Successful Responses

34

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.yabistar.com

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
34 2026-08-25 12:07 639232556111768563
3 ms 61.216.180.60
33 2026-08-25 11:50 639232545839529039
584 ms 61.216.180.60
32 2026-08-25 11:32 639232535349285207
5 ms 61.216.180.60
31 2026-08-25 11:15 639232524938080723
619 ms 61.216.180.60
30 2026-08-25 10:21 639232492740373468
585 ms 61.216.180.60
29 2026-08-25 10:04 639232482235303141
600 ms 61.216.180.60
28 2026-08-25 09:46 639232471861770303
598 ms 61.216.180.60
27 2026-08-25 09:29 639232461630217327
602 ms 61.216.180.60
26 2026-08-25 09:12 639232451282965990
604 ms 61.216.180.60
25 2026-08-25 08:55 639232440814614938
5 ms 61.216.180.60
24 2026-08-25 08:37 639232430410720425
589 ms 61.216.180.60
23 2026-08-25 08:20 639232420003096185
591 ms 61.216.180.60
22 2026-08-25 08:03 639232409467287444
582 ms 61.216.180.60
21 2026-08-25 07:45 639232399077195997
583 ms 61.216.180.60
20 2026-08-25 07:28 639232388731528337
598 ms 61.216.180.60
19 2026-08-25 07:10 639232378288598612
601 ms 61.216.180.60
18 2026-08-25 06:17 639232346196373643
575 ms 61.216.180.60
17 2026-08-25 06:00 639232336112370741
577 ms 61.216.180.60
16 2026-08-25 05:43 639232326146508970
229 ms 61.216.180.60
15 2026-08-25 05:27 639232316189381720
4 ms 61.216.180.60
14 2026-08-25 05:10 639232306217998913
3 ms 61.216.180.60
13 2026-08-25 04:53 639232296255744174
3 ms 61.216.180.60
12 2026-08-25 04:37 639232286095760789
370 ms 61.216.180.60
11 2026-08-25 04:20 639232276086186273
601 ms 61.216.180.60
10 2026-08-25 04:03 639232265900986425
582 ms 61.216.180.60
9 2026-08-25 03:46 639232255723518075
586 ms 61.216.180.60
8 2026-08-25 03:29 639232245484452890
588 ms 61.216.180.60
7 2026-08-25 03:12 639232235157175331
582 ms 61.216.180.60
6 2026-08-25 02:19 639232203197189095
608 ms 61.216.180.60
5 2026-08-25 02:01 639232192844564298
584 ms 61.216.180.60
4 2026-08-25 01:44 639232182496008942
601 ms 61.216.180.60
3 2026-08-25 01:27 639232172197053132
604 ms 61.216.180.60
2 2026-08-25 00:33 639232140250307418
622 ms 61.216.180.60
1 2026-08-25 00:17 639232129927860324
592 ms 61.216.180.60