DNS response history for ns1.netmax.com.tr

ns1.netmax.com.tr 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 31 DNS check records, 31 successful responses, 0 failed responses, and 537 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.netmax.com.tr.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

537 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.115.4.59

Most recently resolved hosting IP on selected date

Successful Responses

31

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.netmax.com.tr

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
31 2026-08-25 11:05 639232524938080723
4138 ms 212.115.4.59
30 2026-08-25 10:11 639232492740373468
86 ms 212.115.4.59
29 2026-08-25 09:53 639232482235303141
2050 ms 212.115.4.59
28 2026-08-25 09:36 639232471861770303
89 ms 212.115.4.59
27 2026-08-25 09:19 639232461630217327
71 ms 212.115.4.59
26 2026-08-25 09:02 639232451282965990
128 ms 212.115.4.59
25 2026-08-25 08:44 639232440814614938
90 ms 212.115.4.59
24 2026-08-25 08:27 639232430410720425
54 ms 212.115.4.59
23 2026-08-25 08:10 639232420003096185
80 ms 212.115.4.59
22 2026-08-25 07:52 639232409467287444
94 ms 212.115.4.59
21 2026-08-25 07:35 639232399077195997
83 ms 212.115.4.59
20 2026-08-25 07:18 639232388731528337
99 ms 212.115.4.59
19 2026-08-25 07:00 639232378288598612
2094 ms 212.115.4.59
18 2026-08-25 06:07 639232346196373643
107 ms 212.115.4.59
17 2026-08-25 05:50 639232336112370741
132 ms 212.115.4.59
16 2026-08-25 05:33 639232326146508970
83 ms 212.115.4.59
15 2026-08-25 05:17 639232316189381720
80 ms 212.115.4.59
14 2026-08-25 05:00 639232306217998913
11 ms 212.115.4.59
13 2026-08-25 04:44 639232296255744174
48 ms 212.115.4.59
12 2026-08-25 04:26 639232286095760789
95 ms 212.115.4.59
11 2026-08-25 04:10 639232276086186273
83 ms 212.115.4.59
10 2026-08-25 03:53 639232265900986425
8 ms 212.115.4.59
9 2026-08-25 03:36 639232255723518075
68 ms 212.115.4.59
8 2026-08-25 03:19 639232245484452890
96 ms 212.115.4.59
7 2026-08-25 03:02 639232235157175331
123 ms 212.115.4.59
6 2026-08-25 02:08 639232203197189095
82 ms 212.115.4.59
5 2026-08-25 01:51 639232192844564298
77 ms 212.115.4.59
4 2026-08-25 01:34 639232182496008942
2064 ms 212.115.4.59
3 2026-08-25 01:17 639232172197053132
2128 ms 212.115.4.59
2 2026-08-25 00:23 639232140250307418
2071 ms 212.115.4.59
1 2026-08-25 00:06 639232129927860324
128 ms 212.115.4.59