DNS response history for ns2.yabertec.com

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

38

Historical checks stored for this nameserver on selected date

Average Latency

227 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.126.110.69

Most recently resolved hosting IP on selected date

Successful Responses

38

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.yabertec.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
38 2026-08-25 13:13 639232597643611557
117 ms 209.126.110.69
37 2026-08-25 12:56 639232587225721862
140 ms 209.126.110.69
36 2026-08-25 12:39 639232576780683689
117 ms 209.126.110.69
35 2026-08-25 12:21 639232566381512620
230 ms 209.126.110.69
34 2026-08-25 12:04 639232556111768563
2129 ms 209.126.110.69
33 2026-08-25 11:47 639232545839529039
135 ms 209.126.110.69
32 2026-08-25 11:30 639232535349285207
119 ms 209.126.110.69
31 2026-08-25 11:12 639232524938080723
126 ms 209.126.110.69
30 2026-08-25 10:18 639232492740373468
227 ms 209.126.110.69
29 2026-08-25 10:01 639232482235303141
230 ms 209.126.110.69
28 2026-08-25 09:44 639232471861770303
231 ms 209.126.110.69
27 2026-08-25 09:26 639232461630217327
232 ms 209.126.110.69
26 2026-08-25 09:09 639232451282965990
129 ms 209.126.110.69
25 2026-08-25 08:52 639232440814614938
233 ms 209.126.110.69
24 2026-08-25 08:35 639232430410720425
238 ms 209.126.110.69
23 2026-08-25 08:17 639232420003096185
121 ms 209.126.110.69
22 2026-08-25 08:00 639232409467287444
246 ms 209.126.110.69
21 2026-08-25 07:42 639232399077195997
117 ms 209.126.110.69
20 2026-08-25 07:25 639232388731528337
117 ms 209.126.110.69
19 2026-08-25 07:08 639232378288598612
239 ms 209.126.110.69
18 2026-08-25 06:14 639232346196373643
236 ms 209.126.110.69
17 2026-08-25 05:57 639232336112370741
248 ms 209.126.110.69
16 2026-08-25 05:41 639232326146508970
4 ms 209.126.110.69
15 2026-08-25 05:24 639232316189381720
230 ms 209.126.110.69
14 2026-08-25 05:07 639232306217998913
4 ms 209.126.110.69
13 2026-08-25 04:51 639232296255744174
6 ms 209.126.110.69
12 2026-08-25 04:34 639232286095760789
115 ms 209.126.110.69
11 2026-08-25 04:17 639232276086186273
228 ms 209.126.110.69
10 2026-08-25 04:00 639232265900986425
234 ms 209.126.110.69
9 2026-08-25 03:43 639232255723518075
117 ms 209.126.110.69
8 2026-08-25 03:26 639232245484452890
228 ms 209.126.110.69
7 2026-08-25 03:09 639232235157175331
119 ms 209.126.110.69
6 2026-08-25 02:16 639232203197189095
235 ms 209.126.110.69
5 2026-08-25 01:59 639232192844564298
233 ms 209.126.110.69
4 2026-08-25 01:41 639232182496008942
229 ms 209.126.110.69
3 2026-08-25 01:24 639232172197053132
232 ms 209.126.110.69
2 2026-08-25 00:31 639232140250307418
229 ms 209.126.110.69
1 2026-08-25 00:14 639232129927860324
228 ms 209.126.110.69