DNS response history for ns1.myezykartwellness.com

ns1.myezykartwellness.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-24. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 278 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 ns1.myezykartwellness.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

278 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.235.106.104

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 ns1.myezykartwellness.com

Showing DNS history for 2026-08-24 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-24 12:24 639231703815441688
302 ms 103.235.106.104
29 2026-08-24 12:07 639231693747052549
327 ms 103.235.106.104
28 2026-08-24 11:51 639231683712487276
184 ms 103.235.106.104
27 2026-08-24 11:34 639231673513573868
298 ms 103.235.106.104
26 2026-08-24 10:41 639231641791249939
299 ms 103.235.106.104
25 2026-08-24 10:24 639231631866211033
4 ms 103.235.106.104
24 2026-08-24 10:07 639231621644955316
13 ms 103.235.106.104
23 2026-08-24 09:50 639231611478799259
319 ms 103.235.106.104
22 2026-08-24 08:58 639231579923718211
317 ms 103.235.106.104
21 2026-08-24 08:41 639231569810702936
304 ms 103.235.106.104
20 2026-08-24 08:24 639231559762411619
291 ms 103.235.106.104
19 2026-08-24 08:07 639231549663595407
290 ms 103.235.106.104
18 2026-08-24 07:15 639231518076817246
286 ms 103.235.106.104
17 2026-08-24 06:58 639231508078650885
16 ms 103.235.106.104
16 2026-08-24 06:41 639231498210697093
300 ms 103.235.106.104
15 2026-08-24 06:25 639231488109699360
302 ms 103.235.106.104
14 2026-08-24 05:33 639231456772510692
5 ms 103.235.106.104
13 2026-08-24 05:16 639231447084631185
1889 ms 103.235.106.104
12 2026-08-24 05:00 639231437208519473
289 ms 103.235.106.104
11 2026-08-24 04:43 639231427209627490
322 ms 103.235.106.104
10 2026-08-24 03:51 639231395791246644
208 ms 103.235.106.104
9 2026-08-24 03:35 639231386075551458
6 ms 103.235.106.104
8 2026-08-24 03:18 639231376208713791
12 ms 103.235.106.104
7 2026-08-24 03:01 639231366170589276
320 ms 103.235.106.104
6 2026-08-24 02:09 639231334732159368
298 ms 103.235.106.104
5 2026-08-24 01:53 639231325035670078
327 ms 103.235.106.104
4 2026-08-24 01:36 639231315132253837
168 ms 103.235.106.104
3 2026-08-24 01:20 639231305014280808
5 ms 103.235.106.104
2 2026-08-24 00:27 639231273779380675
310 ms 103.235.106.104
1 2026-08-24 00:11 639231264180839154
325 ms 103.235.106.104