DNS response history for ns2.inoto.com.tr

ns2.inoto.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-27. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 158 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.inoto.com.tr.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

158 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.173.181.30

Most recently resolved hosting IP on selected date

Successful Responses

28

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

Showing DNS history for 2026-08-27 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
28 2026-08-27 09:06 639234181105879568
31 ms 95.173.181.30
27 2026-08-27 08:49 639234170713214496
117 ms 95.173.181.30
26 2026-08-27 08:31 639234160341037652
2 ms 95.173.181.30
25 2026-08-27 08:14 639234149799404224
72 ms 95.173.181.30
24 2026-08-27 07:57 639234139553286469
138 ms 95.173.181.30
23 2026-08-27 07:03 639234107183588293
29 ms 95.173.181.30
22 2026-08-27 06:46 639234096905435724
20 ms 95.173.181.30
21 2026-08-27 06:29 639234086579410775
230 ms 95.173.181.30
20 2026-08-27 06:12 639234076291157956
2134 ms 95.173.181.30
19 2026-08-27 05:54 639234065981939454
150 ms 95.173.181.30
18 2026-08-27 05:37 639234055548642997
78 ms 95.173.181.30
17 2026-08-27 05:20 639234045267979603
65 ms 95.173.181.30
16 2026-08-27 05:03 639234034999717463
4 ms 95.173.181.30
15 2026-08-27 04:46 639234024739225358
26 ms 95.173.181.30
14 2026-08-27 04:28 639234014311170162
124 ms 95.173.181.30
13 2026-08-27 04:11 639234003806017640
4 ms 95.173.181.30
12 2026-08-27 03:53 639233993356203030
123 ms 95.173.181.30
11 2026-08-27 03:00 639233961301716608
66 ms 95.173.181.30
10 2026-08-27 02:43 639233950834200647
58 ms 95.173.181.30
9 2026-08-27 02:25 639233940431849026
135 ms 95.173.181.30
8 2026-08-27 02:08 639233930110596398
109 ms 95.173.181.30
7 2026-08-27 01:51 639233919705434540
233 ms 95.173.181.30
6 2026-08-27 01:33 639233909452807845
117 ms 95.173.181.30
5 2026-08-27 01:16 639233899096420820
8 ms 95.173.181.30
4 2026-08-27 00:59 639233888707824939
139 ms 95.173.181.30
3 2026-08-27 00:42 639233878461203802
31 ms 95.173.181.30
2 2026-08-27 00:24 639233868060868209
9 ms 95.173.181.30
1 2026-08-27 00:07 639233857450922991
175 ms 95.173.181.30