DNS response history for ns2.vimotur.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

291 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.151.82.82

Most recently resolved hosting IP on selected date

Successful Responses

30

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

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
30 2026-08-27 09:44 639234202117531850
10 ms 91.151.82.82
29 2026-08-27 09:26 639234191649612722
130 ms 91.151.82.82
28 2026-08-27 09:09 639234181105879568
122 ms 91.151.82.82
27 2026-08-27 08:51 639234170713214496
121 ms 91.151.82.82
26 2026-08-27 08:34 639234160341037652
9 ms 91.151.82.82
25 2026-08-27 08:17 639234149799404224
115 ms 91.151.82.82
24 2026-08-27 07:59 639234139553286469
2236 ms 91.151.82.82
23 2026-08-27 07:06 639234107183588293
28 ms 91.151.82.82
22 2026-08-27 06:48 639234096905435724
2156 ms 91.151.82.82
21 2026-08-27 06:31 639234086579410775
113 ms 91.151.82.82
20 2026-08-27 06:14 639234076291157956
7 ms 91.151.82.82
19 2026-08-27 05:57 639234065981939454
111 ms 91.151.82.82
18 2026-08-27 05:40 639234055548642997
123 ms 91.151.82.82
17 2026-08-27 05:22 639234045267979603
117 ms 91.151.82.82
16 2026-08-27 05:05 639234034999717463
126 ms 91.151.82.82
15 2026-08-27 04:48 639234024739225358
50 ms 91.151.82.82
14 2026-08-27 04:31 639234014311170162
11 ms 91.151.82.82
13 2026-08-27 04:13 639234003806017640
90 ms 91.151.82.82
12 2026-08-27 03:56 639233993356203030
67 ms 91.151.82.82
11 2026-08-27 03:03 639233961301716608
122 ms 91.151.82.82
10 2026-08-27 02:45 639233950834200647
12 ms 91.151.82.82
9 2026-08-27 02:28 639233940431849026
119 ms 91.151.82.82
8 2026-08-27 02:10 639233930110596398
71 ms 91.151.82.82
7 2026-08-27 01:53 639233919705434540
60 ms 91.151.82.82
6 2026-08-27 01:36 639233909452807845
104 ms 91.151.82.82
5 2026-08-27 01:19 639233899096420820
121 ms 91.151.82.82
4 2026-08-27 01:01 639233888707824939
122 ms 91.151.82.82
3 2026-08-27 00:44 639233878461203802
55 ms 91.151.82.82
2 2026-08-27 00:27 639233868060868209
2061 ms 91.151.82.82
1 2026-08-27 00:09 639233857450922991
129 ms 91.151.82.82