DNS response history for ns2.yildizbiltek.com

ns2.yildizbiltek.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 35 DNS check records, 35 successful responses, 0 failed responses, and 297 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.yildizbiltek.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

297 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

83.150.213.58

Most recently resolved hosting IP on selected date

Successful Responses

35

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.yildizbiltek.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
35 2026-08-25 12:14 639232566381512620
36 ms 83.150.213.58
34 2026-08-25 11:56 639232556111768563
77 ms 83.150.213.58
33 2026-08-25 11:39 639232545839529039
2062 ms 83.150.213.58
32 2026-08-25 11:22 639232535349285207
12 ms 83.150.213.58
31 2026-08-25 11:05 639232524938080723
77 ms 83.150.213.58
30 2026-08-25 10:11 639232492740373468
93 ms 83.150.213.58
29 2026-08-25 09:54 639232482235303141
2047 ms 83.150.213.58
28 2026-08-25 09:36 639232471861770303
2093 ms 83.150.213.58
27 2026-08-25 09:19 639232461630217327
114 ms 83.150.213.58
26 2026-08-25 09:02 639232451282965990
105 ms 83.150.213.58
25 2026-08-25 08:44 639232440814614938
88 ms 83.150.213.58
24 2026-08-25 08:27 639232430410720425
43 ms 83.150.213.58
23 2026-08-25 08:10 639232420003096185
26 ms 83.150.213.58
22 2026-08-25 07:52 639232409467287444
96 ms 83.150.213.58
21 2026-08-25 07:35 639232399077195997
77 ms 83.150.213.58
20 2026-08-25 07:18 639232388731528337
81 ms 83.150.213.58
19 2026-08-25 07:00 639232378288598612
72 ms 83.150.213.58
18 2026-08-25 06:07 639232346196373643
7 ms 83.150.213.58
17 2026-08-25 05:50 639232336112370741
59 ms 83.150.213.58
16 2026-08-25 05:33 639232326146508970
53 ms 83.150.213.58
15 2026-08-25 05:17 639232316189381720
109 ms 83.150.213.58
14 2026-08-25 05:00 639232306217998913
78 ms 83.150.213.58
13 2026-08-25 04:44 639232296255744174
76 ms 83.150.213.58
12 2026-08-25 04:27 639232286095760789
52 ms 83.150.213.58
11 2026-08-25 04:10 639232276086186273
2091 ms 83.150.213.58
10 2026-08-25 03:53 639232265900986425
76 ms 83.150.213.58
9 2026-08-25 03:36 639232255723518075
105 ms 83.150.213.58
8 2026-08-25 03:19 639232245484452890
83 ms 83.150.213.58
7 2026-08-25 03:02 639232235157175331
34 ms 83.150.213.58
6 2026-08-25 02:08 639232203197189095
50 ms 83.150.213.58
5 2026-08-25 01:51 639232192844564298
55 ms 83.150.213.58
4 2026-08-25 01:34 639232182496008942
43 ms 83.150.213.58
3 2026-08-25 01:17 639232172197053132
31 ms 83.150.213.58
2 2026-08-25 00:23 639232140250307418
101 ms 83.150.213.58
1 2026-08-25 00:06 639232129927860324
77 ms 83.150.213.58