DNS response history for ns2.eg123server.com

ns2.eg123server.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 35 DNS check records, 35 successful responses, 0 failed responses, and 332 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.eg123server.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

332 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.168.249.8

Most recently resolved hosting IP on selected date

Successful Responses

35

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.eg123server.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
35 2026-08-25 12:22 639232566381512620
357 ms 104.168.249.8
34 2026-08-25 12:05 639232556111768563
350 ms 104.168.249.8
33 2026-08-25 11:48 639232545839529039
9 ms 104.168.249.8
32 2026-08-25 11:31 639232535349285207
329 ms 104.168.249.8
31 2026-08-25 11:13 639232524938080723
361 ms 104.168.249.8
30 2026-08-25 10:20 639232492740373468
322 ms 104.168.249.8
29 2026-08-25 10:02 639232482235303141
348 ms 104.168.249.8
28 2026-08-25 09:45 639232471861770303
355 ms 104.168.249.8
27 2026-08-25 09:28 639232461630217327
343 ms 104.168.249.8
26 2026-08-25 09:10 639232451282965990
155 ms 104.168.249.8
25 2026-08-25 08:53 639232440814614938
351 ms 104.168.249.8
24 2026-08-25 08:36 639232430410720425
341 ms 104.168.249.8
23 2026-08-25 08:18 639232420003096185
8 ms 104.168.249.8
22 2026-08-25 08:01 639232409467287444
348 ms 104.168.249.8
21 2026-08-25 07:44 639232399077195997
321 ms 104.168.249.8
20 2026-08-25 07:26 639232388731528337
324 ms 104.168.249.8
19 2026-08-25 07:09 639232378288598612
342 ms 104.168.249.8
18 2026-08-25 06:15 639232346196373643
352 ms 104.168.249.8
17 2026-08-25 05:58 639232336112370741
162 ms 104.168.249.8
16 2026-08-25 05:42 639232326146508970
343 ms 104.168.249.8
15 2026-08-25 05:25 639232316189381720
339 ms 104.168.249.8
14 2026-08-25 05:09 639232306217998913
339 ms 104.168.249.8
13 2026-08-25 04:52 639232296255744174
30 ms 104.168.249.8
12 2026-08-25 04:35 639232286095760789
3 ms 104.168.249.8
11 2026-08-25 04:18 639232276086186273
8 ms 104.168.249.8
10 2026-08-25 04:01 639232265900986425
328 ms 104.168.249.8
9 2026-08-25 03:45 639232255723518075
352 ms 104.168.249.8
8 2026-08-25 03:27 639232245484452890
319 ms 104.168.249.8
7 2026-08-25 03:10 639232235157175331
343 ms 104.168.249.8
6 2026-08-25 02:17 639232203197189095
171 ms 104.168.249.8
5 2026-08-25 02:00 639232192844564298
2226 ms 104.168.249.8
4 2026-08-25 01:43 639232182496008942
337 ms 104.168.249.8
3 2026-08-25 01:25 639232172197053132
316 ms 104.168.249.8
2 2026-08-25 00:32 639232140250307418
344 ms 104.168.249.8
1 2026-08-25 00:15 639232129927860324
353 ms 104.168.249.8