DNS response history for ns2.yhost.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

317 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.160.159.225

Most recently resolved hosting IP on selected date

Successful Responses

37

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.yhost.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
37 2026-08-25 12:57 639232587225721862
311 ms 108.160.159.225
36 2026-08-25 12:40 639232576780683689
347 ms 108.160.159.225
35 2026-08-25 12:23 639232566381512620
261 ms 108.160.159.225
34 2026-08-25 12:05 639232556111768563
149 ms 108.160.159.225
33 2026-08-25 11:48 639232545839529039
317 ms 108.160.159.225
32 2026-08-25 11:31 639232535349285207
150 ms 108.160.159.225
31 2026-08-25 11:13 639232524938080723
325 ms 108.160.159.225
30 2026-08-25 10:20 639232492740373468
333 ms 108.160.159.225
29 2026-08-25 10:03 639232482235303141
336 ms 108.160.159.225
28 2026-08-25 09:45 639232471861770303
340 ms 108.160.159.225
27 2026-08-25 09:28 639232461630217327
315 ms 108.160.159.225
26 2026-08-25 09:11 639232451282965990
325 ms 108.160.159.225
25 2026-08-25 08:53 639232440814614938
153 ms 108.160.159.225
24 2026-08-25 08:36 639232430410720425
342 ms 108.160.159.225
23 2026-08-25 08:19 639232420003096185
165 ms 108.160.159.225
22 2026-08-25 08:01 639232409467287444
167 ms 108.160.159.225
21 2026-08-25 07:44 639232399077195997
324 ms 108.160.159.225
20 2026-08-25 07:26 639232388731528337
328 ms 108.160.159.225
19 2026-08-25 07:09 639232378288598612
2164 ms 108.160.159.225
18 2026-08-25 06:15 639232346196373643
368 ms 108.160.159.225
17 2026-08-25 05:58 639232336112370741
147 ms 108.160.159.225
16 2026-08-25 05:42 639232326146508970
328 ms 108.160.159.225
15 2026-08-25 05:25 639232316189381720
193 ms 108.160.159.225
14 2026-08-25 05:09 639232306217998913
157 ms 108.160.159.225
13 2026-08-25 04:52 639232296255744174
150 ms 108.160.159.225
12 2026-08-25 04:35 639232286095760789
321 ms 108.160.159.225
11 2026-08-25 04:18 639232276086186273
315 ms 108.160.159.225
10 2026-08-25 04:02 639232265900986425
320 ms 108.160.159.225
9 2026-08-25 03:45 639232255723518075
184 ms 108.160.159.225
8 2026-08-25 03:28 639232245484452890
155 ms 108.160.159.225
7 2026-08-25 03:10 639232235157175331
321 ms 108.160.159.225
6 2026-08-25 02:17 639232203197189095
321 ms 108.160.159.225
5 2026-08-25 02:00 639232192844564298
321 ms 108.160.159.225
4 2026-08-25 01:43 639232182496008942
169 ms 108.160.159.225
3 2026-08-25 01:25 639232172197053132
179 ms 108.160.159.225
2 2026-08-25 00:32 639232140250307418
333 ms 108.160.159.225
1 2026-08-25 00:15 639232129927860324
309 ms 108.160.159.225