DNS response history for ns2.yemekle.com

ns2.yemekle.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 31 DNS check records, 30 successful responses, 1 failed responses, and 246 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.yemekle.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

246 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

207.180.192.11

Most recently resolved hosting IP on selected date

Successful Responses

30

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.yemekle.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
31 2026-08-25 11:03 639232524938080723
56 ms 207.180.192.11
30 2026-08-25 10:09 639232492740373468
38 ms 207.180.192.11
29 2026-08-25 09:52 639232482235303141
72 ms 207.180.192.11
28 2026-08-25 09:34 639232471861770303
8 ms 207.180.192.11
27 2026-08-25 09:17 639232461630217327
84 ms 207.180.192.11
26 2026-08-25 09:00 639232451282965990
63 ms 207.180.192.11
25 2026-08-25 08:43 639232440814614938
44 ms 207.180.192.11
24 2026-08-25 08:25 639232430410720425
47 ms 207.180.192.11
23 2026-08-25 08:08 639232420003096185
65 ms 207.180.192.11
22 2026-08-25 07:50 639232409467287444
41 ms 207.180.192.11
21 2026-08-25 07:33 639232399077195997
18 ms 207.180.192.11
20 2026-08-25 07:16 639232388731528337
37 ms 207.180.192.11
19 2026-08-25 06:59 639232378288598612
2040 ms 207.180.192.11
18 2026-08-25 06:05 639232346196373643
30 ms 207.180.192.11
17 2026-08-25 05:48 639232336112370741
47 ms 207.180.192.11
16 2026-08-25 05:32 639232326146508970
69 ms 207.180.192.11
15 2026-08-25 05:15 639232316189381720
4 ms 207.180.192.11
14 2026-08-25 04:58 639232306217998913
33 ms 207.180.192.11
13 2026-08-25 04:42 639232296255744174
79 ms 207.180.192.11
12 2026-08-25 04:25 639232286095760789
-
11 2026-08-25 04:08 639232276086186273
8 ms 207.180.192.11
10 2026-08-25 03:51 639232265900986425
24 ms 207.180.192.11
9 2026-08-25 03:34 639232255723518075
74 ms 207.180.192.11
8 2026-08-25 03:17 639232245484452890
44 ms 207.180.192.11
7 2026-08-25 03:00 639232235157175331
30 ms 207.180.192.11
6 2026-08-25 02:07 639232203197189095
35 ms 207.180.192.11
5 2026-08-25 01:49 639232192844564298
91 ms 207.180.192.11
4 2026-08-25 01:32 639232182496008942
2021 ms 207.180.192.11
3 2026-08-25 01:15 639232172197053132
68 ms 207.180.192.11
2 2026-08-25 00:22 639232140250307418
43 ms 207.180.192.11
1 2026-08-25 00:04 639232129927860324
2061 ms 207.180.192.11