DNS response history for ns2.elazigaday.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

274 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.102.5.130

Most recently resolved hosting IP on selected date

Successful Responses

36

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.elazigaday.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
36 2026-08-25 12:32 639232576780683689
161 ms 94.102.5.130
35 2026-08-25 12:15 639232566381512620
60 ms 94.102.5.130
34 2026-08-25 11:58 639232556111768563
137 ms 94.102.5.130
33 2026-08-25 11:41 639232545839529039
145 ms 94.102.5.130
32 2026-08-25 11:23 639232535349285207
72 ms 94.102.5.130
31 2026-08-25 11:06 639232524938080723
148 ms 94.102.5.130
30 2026-08-25 10:12 639232492740373468
12 ms 94.102.5.130
29 2026-08-25 09:55 639232482235303141
120 ms 94.102.5.130
28 2026-08-25 09:37 639232471861770303
133 ms 94.102.5.130
27 2026-08-25 09:20 639232461630217327
112 ms 94.102.5.130
26 2026-08-25 09:03 639232451282965990
129 ms 94.102.5.130
25 2026-08-25 08:46 639232440814614938
123 ms 94.102.5.130
24 2026-08-25 08:28 639232430410720425
68 ms 94.102.5.130
23 2026-08-25 08:11 639232420003096185
128 ms 94.102.5.130
22 2026-08-25 07:54 639232409467287444
144 ms 94.102.5.130
21 2026-08-25 07:36 639232399077195997
73 ms 94.102.5.130
20 2026-08-25 07:19 639232388731528337
128 ms 94.102.5.130
19 2026-08-25 07:02 639232378288598612
119 ms 94.102.5.130
18 2026-08-25 06:08 639232346196373643
150 ms 94.102.5.130
17 2026-08-25 05:51 639232336112370741
91 ms 94.102.5.130
16 2026-08-25 05:35 639232326146508970
19 ms 94.102.5.130
15 2026-08-25 05:18 639232316189381720
121 ms 94.102.5.130
14 2026-08-25 05:01 639232306217998913
131 ms 94.102.5.130
13 2026-08-25 04:45 639232296255744174
118 ms 94.102.5.130
12 2026-08-25 04:28 639232286095760789
68 ms 94.102.5.130
11 2026-08-25 04:11 639232276086186273
130 ms 94.102.5.130
10 2026-08-25 03:54 639232265900986425
65 ms 94.102.5.130
9 2026-08-25 03:37 639232255723518075
59 ms 94.102.5.130
8 2026-08-25 03:20 639232245484452890
4061 ms 94.102.5.130
7 2026-08-25 03:03 639232235157175331
118 ms 94.102.5.130
6 2026-08-25 02:10 639232203197189095
124 ms 94.102.5.130
5 2026-08-25 01:52 639232192844564298
150 ms 94.102.5.130
4 2026-08-25 01:35 639232182496008942
124 ms 94.102.5.130
3 2026-08-25 01:18 639232172197053132
166 ms 94.102.5.130
2 2026-08-25 00:25 639232140250307418
2083 ms 94.102.5.130
1 2026-08-25 00:08 639232129927860324
65 ms 94.102.5.130