DNS response history for ns2.egeomed.com

ns2.egeomed.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, 37 successful responses, 1 failed responses, and 339 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.egeomed.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

339 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.164.144.120

Most recently resolved hosting IP on selected date

Successful Responses

37

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.egeomed.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:13 639232597643611557
2130 ms 95.164.144.120
37 2026-08-25 12:55 639232587225721862
107 ms 95.164.144.120
36 2026-08-25 12:38 639232576780683689
112 ms 95.164.144.120
35 2026-08-25 12:21 639232566381512620
111 ms 95.164.144.120
34 2026-08-25 12:03 639232556111768563
104 ms 95.164.144.120
33 2026-08-25 11:46 639232545839529039
133 ms 95.164.144.120
32 2026-08-25 11:29 639232535349285207
136 ms 95.164.144.120
31 2026-08-25 11:12 639232524938080723
112 ms 95.164.144.120
30 2026-08-25 10:18 639232492740373468
104 ms 95.164.144.120
29 2026-08-25 10:01 639232482235303141
2007 ms 95.164.144.120
28 2026-08-25 09:43 639232471861770303
250 ms 95.164.144.120
27 2026-08-25 09:26 639232461630217327
185 ms 95.164.144.120
26 2026-08-25 09:09 639232451282965990
202 ms 95.164.144.120
25 2026-08-25 08:51 639232440814614938
137 ms 95.164.144.120
24 2026-08-25 08:34 639232430410720425
115 ms 95.164.144.120
23 2026-08-25 08:17 639232420003096185
123 ms 95.164.144.120
22 2026-08-25 07:59 639232409467287444
109 ms 95.164.144.120
21 2026-08-25 07:42 639232399077195997
132 ms 95.164.144.120
20 2026-08-25 07:25 639232388731528337
155 ms 95.164.144.120
19 2026-08-25 07:07 639232378288598612
105 ms 95.164.144.120
18 2026-08-25 06:14 639232346196373643
4 ms 95.164.144.120
17 2026-08-25 05:57 639232336112370741
100 ms 95.164.144.120
16 2026-08-25 05:40 639232326146508970
136 ms 95.164.144.120
15 2026-08-25 05:23 639232316189381720
120 ms 95.164.144.120
14 2026-08-25 05:07 639232306217998913
3 ms 95.164.144.120
13 2026-08-25 04:50 639232296255744174
2194 ms 95.164.144.120
12 2026-08-25 04:33 639232286095760789
2 ms 95.164.144.120
11 2026-08-25 04:16 639232276086186273
106 ms 95.164.144.120
10 2026-08-25 04:00 639232265900986425
104 ms 95.164.144.120
9 2026-08-25 03:43 639232255723518075
2214 ms 95.164.144.120
8 2026-08-25 03:26 639232245484452890
205 ms 95.164.144.120
7 2026-08-25 03:09 639232235157175331
150 ms 95.164.144.120
6 2026-08-25 02:15 639232203197189095
135 ms 95.164.144.120
5 2026-08-25 01:58 639232192844564298
150 ms 95.164.144.120
4 2026-08-25 01:41 639232182496008942
144 ms 95.164.144.120
3 2026-08-25 01:24 639232172197053132
100 ms 95.164.144.120
2 2026-08-25 00:30 639232140250307418
-
1 2026-08-25 00:13 639232129927860324
119 ms 95.164.144.120