DNS response history for ns2.yeri.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

349 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.196.126.247

Most recently resolved hosting IP on selected date

Successful Responses

34

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.yeri.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
34 2026-08-25 12:01 639232556111768563
216 ms 104.196.126.247
33 2026-08-25 11:44 639232545839529039
221 ms 104.196.126.247
32 2026-08-25 11:27 639232535349285207
218 ms 104.196.126.247
31 2026-08-25 11:09 639232524938080723
182 ms 104.196.126.247
30 2026-08-25 10:16 639232492740373468
224 ms 104.196.126.247
29 2026-08-25 09:58 639232482235303141
233 ms 104.196.126.247
28 2026-08-25 09:41 639232471861770303
2019 ms 104.196.126.247
27 2026-08-25 09:24 639232461630217327
232 ms 104.196.126.247
26 2026-08-25 09:07 639232451282965990
229 ms 104.196.126.247
25 2026-08-25 08:49 639232440814614938
241 ms 104.196.126.247
24 2026-08-25 08:32 639232430410720425
235 ms 104.196.126.247
23 2026-08-25 08:14 639232420003096185
141 ms 104.196.126.247
22 2026-08-25 07:57 639232409467287444
247 ms 104.196.126.247
21 2026-08-25 07:40 639232399077195997
132 ms 104.196.126.247
20 2026-08-25 07:22 639232388731528337
239 ms 104.196.126.247
19 2026-08-25 07:05 639232378288598612
232 ms 104.196.126.247
18 2026-08-25 06:11 639232346196373643
2124 ms 104.196.126.247
17 2026-08-25 05:54 639232336112370741
151 ms 104.196.126.247
16 2026-08-25 05:38 639232326146508970
232 ms 104.196.126.247
15 2026-08-25 05:21 639232316189381720
9 ms 104.196.126.247
14 2026-08-25 05:05 639232306217998913
232 ms 104.196.126.247
13 2026-08-25 04:48 639232296255744174
177 ms 104.196.126.247
12 2026-08-25 04:31 639232286095760789
245 ms 104.196.126.247
11 2026-08-25 04:14 639232276086186273
12 ms 104.196.126.247
10 2026-08-25 03:58 639232265900986425
277 ms 104.196.126.247
9 2026-08-25 03:41 639232255723518075
125 ms 104.196.126.247
8 2026-08-25 03:24 639232245484452890
11 ms 104.196.126.247
7 2026-08-25 03:06 639232235157175331
2007 ms 104.196.126.247
6 2026-08-25 02:13 639232203197189095
232 ms 104.196.126.247
5 2026-08-25 01:56 639232192844564298
162 ms 104.196.126.247
4 2026-08-25 01:39 639232182496008942
233 ms 104.196.126.247
3 2026-08-25 01:21 639232172197053132
140 ms 104.196.126.247
2 2026-08-25 00:28 639232140250307418
7 ms 104.196.126.247
1 2026-08-25 00:11 639232129927860324
246 ms 104.196.126.247