DNS response history for ns2.yayemo.com

ns2.yayemo.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 356 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.yayemo.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

356 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

109.203.117.175

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.yayemo.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:09 639232597643611557
4 ms 109.203.117.175
37 2026-08-25 12:52 639232587225721862
54 ms 109.203.117.175
36 2026-08-25 12:34 639232576780683689
39 ms 109.203.117.175
35 2026-08-25 12:17 639232566381512620
11 ms 109.203.117.175
34 2026-08-25 12:00 639232556111768563
14 ms 109.203.117.175
33 2026-08-25 11:43 639232545839529039
13 ms 109.203.117.175
32 2026-08-25 11:25 639232535349285207
46 ms 109.203.117.175
31 2026-08-25 11:08 639232524938080723
41 ms 109.203.117.175
30 2026-08-25 10:14 639232492740373468
48 ms 109.203.117.175
29 2026-08-25 09:57 639232482235303141
82 ms 109.203.117.175
28 2026-08-25 09:39 639232471861770303
70 ms 109.203.117.175
27 2026-08-25 09:22 639232461630217327
26 ms 109.203.117.175
26 2026-08-25 09:05 639232451282965990
49 ms 109.203.117.175
25 2026-08-25 08:48 639232440814614938
50 ms 109.203.117.175
24 2026-08-25 08:30 639232430410720425
74 ms 109.203.117.175
23 2026-08-25 08:13 639232420003096185
42 ms 109.203.117.175
22 2026-08-25 07:56 639232409467287444
4035 ms 109.203.117.175
21 2026-08-25 07:38 639232399077195997
44 ms 109.203.117.175
20 2026-08-25 07:21 639232388731528337
44 ms 109.203.117.175
19 2026-08-25 07:03 639232378288598612
42 ms 109.203.117.175
18 2026-08-25 06:10 639232346196373643
4030 ms 109.203.117.175
17 2026-08-25 05:53 639232336112370741
37 ms 109.203.117.175
16 2026-08-25 05:36 639232326146508970
6 ms 109.203.117.175
15 2026-08-25 05:20 639232316189381720
3 ms 109.203.117.175
14 2026-08-25 05:03 639232306217998913
43 ms 109.203.117.175
13 2026-08-25 04:47 639232296255744174
37 ms 109.203.117.175
12 2026-08-25 04:30 639232286095760789
45 ms 109.203.117.175
11 2026-08-25 04:13 639232276086186273
41 ms 109.203.117.175
10 2026-08-25 03:56 639232265900986425
4058 ms 109.203.117.175
9 2026-08-25 03:39 639232255723518075
52 ms 109.203.117.175
8 2026-08-25 03:22 639232245484452890
30 ms 109.203.117.175
7 2026-08-25 03:05 639232235157175331
40 ms 109.203.117.175
6 2026-08-25 02:12 639232203197189095
87 ms 109.203.117.175
5 2026-08-25 01:54 639232192844564298
25 ms 109.203.117.175
4 2026-08-25 01:37 639232182496008942
26 ms 109.203.117.175
3 2026-08-25 01:20 639232172197053132
27 ms 109.203.117.175
2 2026-08-25 00:27 639232140250307418
41 ms 109.203.117.175
1 2026-08-25 00:09 639232129927860324
73 ms 109.203.117.175