DNS response history for ns2.yeehost.net

ns2.yeehost.net 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 30 DNS check records, 30 successful responses, 0 failed responses, and 283 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.yeehost.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

283 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.115.19.168

Most recently resolved hosting IP on selected date

Successful Responses

30

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.yeehost.net

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
30 2026-08-25 10:18 639232492740373468
257 ms 50.115.19.168
29 2026-08-25 10:01 639232482235303141
256 ms 50.115.19.168
28 2026-08-25 09:43 639232471861770303
260 ms 50.115.19.168
27 2026-08-25 09:26 639232461630217327
255 ms 50.115.19.168
26 2026-08-25 09:09 639232451282965990
123 ms 50.115.19.168
25 2026-08-25 08:51 639232440814614938
260 ms 50.115.19.168
24 2026-08-25 08:34 639232430410720425
257 ms 50.115.19.168
23 2026-08-25 08:17 639232420003096185
264 ms 50.115.19.168
22 2026-08-25 07:59 639232409467287444
7 ms 50.115.19.168
21 2026-08-25 07:42 639232399077195997
138 ms 50.115.19.168
20 2026-08-25 07:24 639232388731528337
262 ms 50.115.19.168
19 2026-08-25 07:07 639232378288598612
260 ms 50.115.19.168
18 2026-08-25 06:13 639232346196373643
258 ms 50.115.19.168
17 2026-08-25 05:56 639232336112370741
271 ms 50.115.19.168
16 2026-08-25 05:40 639232326146508970
128 ms 50.115.19.168
15 2026-08-25 05:23 639232316189381720
127 ms 50.115.19.168
14 2026-08-25 05:07 639232306217998913
257 ms 50.115.19.168
13 2026-08-25 04:50 639232296255744174
257 ms 50.115.19.168
12 2026-08-25 04:33 639232286095760789
119 ms 50.115.19.168
11 2026-08-25 04:16 639232276086186273
259 ms 50.115.19.168
10 2026-08-25 04:00 639232265900986425
151 ms 50.115.19.168
9 2026-08-25 03:43 639232255723518075
264 ms 50.115.19.168
8 2026-08-25 03:26 639232245484452890
266 ms 50.115.19.168
7 2026-08-25 03:08 639232235157175331
117 ms 50.115.19.168
6 2026-08-25 02:15 639232203197189095
259 ms 50.115.19.168
5 2026-08-25 01:58 639232192844564298
2127 ms 50.115.19.168
4 2026-08-25 01:41 639232182496008942
265 ms 50.115.19.168
3 2026-08-25 01:23 639232172197053132
258 ms 50.115.19.168
2 2026-08-25 00:30 639232140250307418
265 ms 50.115.19.168
1 2026-08-25 00:13 639232129927860324
257 ms 50.115.19.168