DNS response history for ns2.ozgur.news

ns2.ozgur.news 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 30 DNS check records, 29 successful responses, 1 failed responses, and 313 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.ozgur.news.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

313 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.244.88.82

Most recently resolved hosting IP on selected date

Successful Responses

29

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.ozgur.news

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
30 2026-08-25 10:15 639232492740373468
2113 ms 199.244.88.82
29 2026-08-25 09:58 639232482235303141
106 ms 199.244.88.82
28 2026-08-25 09:40 639232471861770303
213 ms 199.244.88.82
27 2026-08-25 09:23 639232461630217327
267 ms 199.244.88.82
26 2026-08-25 09:06 639232451282965990
216 ms 199.244.88.82
25 2026-08-25 08:48 639232440814614938
218 ms 199.244.88.82
24 2026-08-25 08:31 639232430410720425
170 ms 199.244.88.82
23 2026-08-25 08:14 639232420003096185
124 ms 199.244.88.82
22 2026-08-25 07:56 639232409467287444
238 ms 199.244.88.82
21 2026-08-25 07:39 639232399077195997
223 ms 199.244.88.82
20 2026-08-25 07:22 639232388731528337
2122 ms 199.244.88.82
19 2026-08-25 07:04 639232378288598612
132 ms 199.244.88.82
18 2026-08-25 06:11 639232346196373643
455 ms 199.244.88.82
17 2026-08-25 05:54 639232336112370741
136 ms 199.244.88.82
16 2026-08-25 05:37 639232326146508970
104 ms 199.244.88.82
15 2026-08-25 05:21 639232316189381720
223 ms 199.244.88.82
14 2026-08-25 05:04 639232306217998913
113 ms 199.244.88.82
13 2026-08-25 04:47 639232296255744174
117 ms 199.244.88.82
12 2026-08-25 04:31 639232286095760789
213 ms 199.244.88.82
11 2026-08-25 04:14 639232276086186273
-
10 2026-08-25 03:57 639232265900986425
112 ms 199.244.88.82
9 2026-08-25 03:40 639232255723518075
105 ms 199.244.88.82
8 2026-08-25 03:23 639232245484452890
125 ms 199.244.88.82
7 2026-08-25 03:06 639232235157175331
111 ms 199.244.88.82
6 2026-08-25 02:12 639232203197189095
210 ms 199.244.88.82
5 2026-08-25 01:55 639232192844564298
210 ms 199.244.88.82
4 2026-08-25 01:38 639232182496008942
223 ms 199.244.88.82
3 2026-08-25 01:21 639232172197053132
234 ms 199.244.88.82
2 2026-08-25 00:27 639232140250307418
134 ms 199.244.88.82
1 2026-08-25 00:10 639232129927860324
120 ms 199.244.88.82