DNS response history for ns2.vimms.net

ns2.vimms.net 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 37 DNS check records, 37 successful responses, 0 failed responses, and 184 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.vimms.net.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

184 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.206.228.76

Most recently resolved hosting IP on selected date

Successful Responses

37

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.vimms.net

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
37 2026-08-27 12:28 639234296664302575
217 ms 74.206.228.76
36 2026-08-27 12:10 639234286253196126
788 ms 74.206.228.76
35 2026-08-27 11:17 639234253963286387
100 ms 74.206.228.76
34 2026-08-27 10:59 639234243654907465
210 ms 74.206.228.76
33 2026-08-27 10:42 639234233269654413
109 ms 74.206.228.76
32 2026-08-27 10:25 639234222943951923
101 ms 74.206.228.76
31 2026-08-27 10:08 639234212558002823
199 ms 74.206.228.76
30 2026-08-27 09:50 639234202117531850
206 ms 74.206.228.76
29 2026-08-27 09:33 639234191649612722
208 ms 74.206.228.76
28 2026-08-27 09:15 639234181105879568
209 ms 74.206.228.76
27 2026-08-27 08:58 639234170713214496
109 ms 74.206.228.76
26 2026-08-27 08:41 639234160341037652
207 ms 74.206.228.76
25 2026-08-27 08:23 639234149799404224
208 ms 74.206.228.76
24 2026-08-27 08:05 639234139553286469
207 ms 74.206.228.76
23 2026-08-27 07:12 639234107183588293
211 ms 74.206.228.76
22 2026-08-27 06:55 639234096905435724
206 ms 74.206.228.76
21 2026-08-27 06:38 639234086579410775
102 ms 74.206.228.76
20 2026-08-27 06:20 639234076291157956
107 ms 74.206.228.76
19 2026-08-27 06:03 639234065981939454
99 ms 74.206.228.76
18 2026-08-27 05:46 639234055548642997
203 ms 74.206.228.76
17 2026-08-27 05:29 639234045267979603
210 ms 74.206.228.76
16 2026-08-27 05:12 639234034999717463
207 ms 74.206.228.76
15 2026-08-27 04:54 639234024739225358
205 ms 74.206.228.76
14 2026-08-27 04:37 639234014311170162
102 ms 74.206.228.76
13 2026-08-27 04:20 639234003806017640
105 ms 74.206.228.76
12 2026-08-27 04:02 639233993356203030
106 ms 74.206.228.76
11 2026-08-27 03:09 639233961301716608
98 ms 74.206.228.76
10 2026-08-27 02:52 639233950834200647
206 ms 74.206.228.76
9 2026-08-27 02:34 639233940431849026
104 ms 74.206.228.76
8 2026-08-27 02:17 639233930110596398
100 ms 74.206.228.76
7 2026-08-27 02:00 639233919705434540
354 ms 74.206.228.76
6 2026-08-27 01:43 639233909452807845
209 ms 74.206.228.76
5 2026-08-27 01:25 639233899096420820
98 ms 74.206.228.76
4 2026-08-27 01:08 639233888707824939
205 ms 74.206.228.76
3 2026-08-27 00:51 639233878461203802
103 ms 74.206.228.76
2 2026-08-27 00:33 639233868060868209
197 ms 74.206.228.76
1 2026-08-27 00:16 639233857450922991
205 ms 74.206.228.76