DNS response history for ns2.yogabearpc.com

ns2.yogabearpc.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-24. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 304 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.yogabearpc.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

304 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.167.201.110

Most recently resolved hosting IP on selected date

Successful Responses

36

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

Showing DNS history for 2026-08-24 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
36 2026-08-24 15:07 639231807961539652
6 ms 199.167.201.110
35 2026-08-24 14:49 639231797631669865
11 ms 199.167.201.110
34 2026-08-24 13:57 639231765923559455
19 ms 199.167.201.110
33 2026-08-24 13:40 639231755868832964
45 ms 199.167.201.110
32 2026-08-24 13:23 639231745628278877
22 ms 199.167.201.110
31 2026-08-24 13:06 639231735407682062
21 ms 199.167.201.110
30 2026-08-24 12:13 639231703815441688
2064 ms 199.167.201.110
29 2026-08-24 11:56 639231693747052549
23 ms 199.167.201.110
28 2026-08-24 11:40 639231683712487276
25 ms 199.167.201.110
27 2026-08-24 11:23 639231673513573868
2041 ms 199.167.201.110
26 2026-08-24 10:30 639231641791249939
24 ms 199.167.201.110
25 2026-08-24 10:13 639231631866211033
16 ms 199.167.201.110
24 2026-08-24 09:56 639231621644955316
12 ms 199.167.201.110
23 2026-08-24 09:39 639231611478799259
48 ms 199.167.201.110
22 2026-08-24 08:47 639231579923718211
44 ms 199.167.201.110
21 2026-08-24 08:30 639231569810702936
21 ms 199.167.201.110
20 2026-08-24 08:13 639231559762411619
8 ms 199.167.201.110
19 2026-08-24 07:56 639231549663595407
20 ms 199.167.201.110
18 2026-08-24 07:03 639231518076817246
14 ms 199.167.201.110
17 2026-08-24 06:47 639231508078650885
36 ms 199.167.201.110
16 2026-08-24 06:30 639231498210697093
39 ms 199.167.201.110
15 2026-08-24 06:14 639231488109699360
27 ms 199.167.201.110
14 2026-08-24 05:21 639231456772510692
42 ms 199.167.201.110
13 2026-08-24 05:05 639231447084631185
21 ms 199.167.201.110
12 2026-08-24 04:49 639231437208519473
11 ms 199.167.201.110
11 2026-08-24 04:32 639231427209627490
42 ms 199.167.201.110
10 2026-08-24 03:40 639231395791246644
72 ms 199.167.201.110
9 2026-08-24 03:23 639231386075551458
24 ms 199.167.201.110
8 2026-08-24 03:07 639231376208713791
4030 ms 199.167.201.110
7 2026-08-24 02:50 639231366170589276
22 ms 199.167.201.110
6 2026-08-24 01:58 639231334732159368
13 ms 199.167.201.110
5 2026-08-24 01:42 639231325035670078
10 ms 199.167.201.110
4 2026-08-24 01:25 639231315132253837
2019 ms 199.167.201.110
3 2026-08-24 01:08 639231305014280808
14 ms 199.167.201.110
2 2026-08-24 00:16 639231273779380675
6 ms 199.167.201.110
1 2026-08-24 00:00 639231264180839154
22 ms 199.167.201.110