DNS response history for ns2.in4tur.com

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

27

Historical checks stored for this nameserver on selected date

Average Latency

190 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

195.122.202.149

Most recently resolved hosting IP on selected date

Successful Responses

27

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.in4tur.com

Showing DNS history for 2026-08-26 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
27 2026-08-26 08:54 639233308387917838
27 ms 195.122.202.149
26 2026-08-26 08:36 639233297961740122
38 ms 195.122.202.149
25 2026-08-26 08:19 639233287487159094
76 ms 195.122.202.149
24 2026-08-26 08:01 639233276995531707
63 ms 195.122.202.149
23 2026-08-26 07:44 639233266521568229
44 ms 195.122.202.149
22 2026-08-26 07:26 639233256081047431
25 ms 195.122.202.149
21 2026-08-26 06:32 639233223620132921
46 ms 195.122.202.149
20 2026-08-26 06:15 639233213287814244
47 ms 195.122.202.149
19 2026-08-26 05:58 639233202925983161
36 ms 195.122.202.149
18 2026-08-26 05:41 639233192644780696
27 ms 195.122.202.149
17 2026-08-26 05:24 639233182401183833
73 ms 195.122.202.149
16 2026-08-26 05:07 639233172074181051
22 ms 195.122.202.149
15 2026-08-26 04:49 639233161808421455
125 ms 195.122.202.149
14 2026-08-26 04:32 639233151357344052
7 ms 195.122.202.149
13 2026-08-26 04:15 639233141034116946
30 ms 195.122.202.149
12 2026-08-26 03:58 639233130828334142
44 ms 195.122.202.149
11 2026-08-26 03:40 639233120373450007
35 ms 195.122.202.149
10 2026-08-26 03:23 639233110066216193
2027 ms 195.122.202.149
9 2026-08-26 02:30 639233078065410564
49 ms 195.122.202.149
8 2026-08-26 02:13 639233067787457832
2011 ms 195.122.202.149
7 2026-08-26 01:56 639233057501801162
68 ms 195.122.202.149
6 2026-08-26 01:38 639233047089431703
59 ms 195.122.202.149
5 2026-08-26 01:21 639233036754790688
7 ms 195.122.202.149
4 2026-08-26 01:04 639233026412602472
33 ms 195.122.202.149
3 2026-08-26 00:46 639233016064066127
35 ms 195.122.202.149
2 2026-08-26 00:29 639233005922655772
30 ms 195.122.202.149
1 2026-08-26 00:12 639232995672256907
37 ms 195.122.202.149