DNS response history for ns1.eosmanline.com

ns1.eosmanline.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 37 DNS check records, 37 successful responses, 0 failed responses, and 220 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.eosmanline.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

220 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

8.8.8.121

Most recently resolved hosting IP on selected date

Successful Responses

37

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.eosmanline.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
37 2026-08-26 12:27 639233434974187439
128 ms 8.8.8.121
36 2026-08-26 12:09 639233424567558554
25 ms 8.8.8.121
35 2026-08-26 11:52 639233414056832719
83 ms 8.8.8.121
34 2026-08-26 11:34 639233403515141099
121 ms 8.8.8.121
33 2026-08-26 10:40 639233370841350248
129 ms 8.8.8.121
32 2026-08-26 10:22 639233360361507238
135 ms 8.8.8.121
31 2026-08-26 10:05 639233350067824371
35 ms 8.8.8.121
30 2026-08-26 09:48 639233339545274518
119 ms 8.8.8.121
29 2026-08-26 09:30 639233329214918079
126 ms 8.8.8.121
28 2026-08-26 09:13 639233318749762337
154 ms 8.8.8.121
27 2026-08-26 08:56 639233308387917838
186 ms 8.8.8.121
26 2026-08-26 08:38 639233297961740122
118 ms 8.8.8.121
25 2026-08-26 08:21 639233287487159094
122 ms 8.8.8.121
24 2026-08-26 08:04 639233276995531707
2119 ms 8.8.8.121
23 2026-08-26 07:46 639233266521568229
79 ms 8.8.8.121
22 2026-08-26 07:29 639233256081047431
122 ms 8.8.8.121
21 2026-08-26 06:35 639233223620132921
154 ms 8.8.8.121
20 2026-08-26 06:17 639233213287814244
118 ms 8.8.8.121
19 2026-08-26 06:00 639233202925983161
86 ms 8.8.8.121
18 2026-08-26 05:43 639233192644780696
77 ms 8.8.8.121
17 2026-08-26 05:26 639233182401183833
77 ms 8.8.8.121
16 2026-08-26 05:09 639233172074181051
117 ms 8.8.8.121
15 2026-08-26 04:51 639233161808421455
83 ms 8.8.8.121
14 2026-08-26 04:34 639233151357344052
200 ms 8.8.8.121
13 2026-08-26 04:17 639233141034116946
119 ms 8.8.8.121
12 2026-08-26 04:00 639233130828334142
135 ms 8.8.8.121
11 2026-08-26 03:43 639233120373450007
121 ms 8.8.8.121
10 2026-08-26 03:25 639233110066216193
153 ms 8.8.8.121
9 2026-08-26 02:32 639233078065410564
119 ms 8.8.8.121
8 2026-08-26 02:15 639233067787457832
117 ms 8.8.8.121
7 2026-08-26 01:58 639233057501801162
79 ms 8.8.8.121
6 2026-08-26 01:40 639233047089431703
50 ms 8.8.8.121
5 2026-08-26 01:23 639233036754790688
2125 ms 8.8.8.121
4 2026-08-26 01:06 639233026412602472
79 ms 8.8.8.121
3 2026-08-26 00:49 639233016064066127
119 ms 8.8.8.121
2 2026-08-26 00:32 639233005922655772
122 ms 8.8.8.121
1 2026-08-26 00:15 639232995672256907
75 ms 8.8.8.121