DNS response history for ns2.myeisely.com

ns2.myeisely.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-26. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 522 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.myeisely.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

522 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.206.228.76

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.myeisely.com

Showing DNS history for 2026-08-26 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-26 12:32 639233434974187439
483 ms 74.206.228.76
37 2026-08-26 12:14 639233424567558554
471 ms 74.206.228.76
36 2026-08-26 11:57 639233414056832719
478 ms 74.206.228.76
35 2026-08-26 11:39 639233403515141099
1602 ms 74.206.228.76
34 2026-08-26 10:45 639233370841350248
481 ms 74.206.228.76
33 2026-08-26 10:27 639233360361507238
477 ms 74.206.228.76
32 2026-08-26 10:10 639233350067824371
469 ms 74.206.228.76
31 2026-08-26 09:53 639233339545274518
472 ms 74.206.228.76
30 2026-08-26 09:35 639233329214918079
468 ms 74.206.228.76
29 2026-08-26 09:18 639233318749762337
480 ms 74.206.228.76
28 2026-08-26 09:01 639233308387917838
476 ms 74.206.228.76
27 2026-08-26 08:43 639233297961740122
473 ms 74.206.228.76
26 2026-08-26 08:26 639233287487159094
472 ms 74.206.228.76
25 2026-08-26 08:09 639233276995531707
476 ms 74.206.228.76
24 2026-08-26 07:51 639233266521568229
476 ms 74.206.228.76
23 2026-08-26 07:33 639233256081047431
468 ms 74.206.228.76
22 2026-08-26 06:39 639233223620132921
473 ms 74.206.228.76
21 2026-08-26 06:22 639233213287814244
492 ms 74.206.228.76
20 2026-08-26 06:05 639233202925983161
467 ms 74.206.228.76
19 2026-08-26 05:48 639233192644780696
475 ms 74.206.228.76
18 2026-08-26 05:30 639233182401183833
481 ms 74.206.228.76
17 2026-08-26 05:13 639233172074181051
517 ms 74.206.228.76
16 2026-08-26 04:56 639233161808421455
475 ms 74.206.228.76
15 2026-08-26 04:39 639233151357344052
467 ms 74.206.228.76
14 2026-08-26 04:22 639233141034116946
33 ms 74.206.228.76
13 2026-08-26 04:05 639233130828334142
1649 ms 74.206.228.76
12 2026-08-26 03:47 639233120373450007
472 ms 74.206.228.76
11 2026-08-26 03:30 639233110066216193
475 ms 74.206.228.76
10 2026-08-26 02:37 639233078065410564
330 ms 74.206.228.76
9 2026-08-26 02:20 639233067787457832
465 ms 74.206.228.76
8 2026-08-26 02:02 639233057501801162
486 ms 74.206.228.76
7 2026-08-26 01:45 639233047089431703
481 ms 74.206.228.76
6 2026-08-26 01:28 639233036754790688
483 ms 74.206.228.76
5 2026-08-26 01:11 639233026412602472
481 ms 74.206.228.76
4 2026-08-26 00:53 639233016064066127
477 ms 74.206.228.76
3 2026-08-26 00:36 639233005922655772
472 ms 74.206.228.76
2 2026-08-26 00:19 639232995672256907
468 ms 74.206.228.76
1 2026-08-26 00:02 639232985300872416
477 ms 74.206.228.76