DNS response history for ns2.milengroup.net

ns2.milengroup.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-24. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 100 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.milengroup.net.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

100 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

167.235.130.180

Most recently resolved hosting IP on selected date

Successful Responses

32

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

Showing DNS history for 2026-08-24 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
32 2026-08-24 13:24 639231745628278877
48 ms 167.235.130.180
31 2026-08-24 13:07 639231735407682062
32 ms 167.235.130.180
30 2026-08-24 12:15 639231703815441688
45 ms 167.235.130.180
29 2026-08-24 11:58 639231693747052549
53 ms 167.235.130.180
28 2026-08-24 11:41 639231683712487276
51 ms 167.235.130.180
27 2026-08-24 11:24 639231673513573868
66 ms 167.235.130.180
26 2026-08-24 10:31 639231641791249939
18 ms 167.235.130.180
25 2026-08-24 10:14 639231631866211033
51 ms 167.235.130.180
24 2026-08-24 09:57 639231621644955316
32 ms 167.235.130.180
23 2026-08-24 09:41 639231611478799259
5 ms 167.235.130.180
22 2026-08-24 08:48 639231579923718211
98 ms 167.235.130.180
21 2026-08-24 08:31 639231569810702936
34 ms 167.235.130.180
20 2026-08-24 08:14 639231559762411619
37 ms 167.235.130.180
19 2026-08-24 07:58 639231549663595407
42 ms 167.235.130.180
18 2026-08-24 07:05 639231518076817246
17 ms 167.235.130.180
17 2026-08-24 06:48 639231508078650885
63 ms 167.235.130.180
16 2026-08-24 06:32 639231498210697093
23 ms 167.235.130.180
15 2026-08-24 06:15 639231488109699360
4 ms 167.235.130.180
14 2026-08-24 05:23 639231456772510692
81 ms 167.235.130.180
13 2026-08-24 05:07 639231447084631185
2 ms 167.235.130.180
12 2026-08-24 04:50 639231437208519473
19 ms 167.235.130.180
11 2026-08-24 04:34 639231427209627490
53 ms 167.235.130.180
10 2026-08-24 03:41 639231395791246644
57 ms 167.235.130.180
9 2026-08-24 03:25 639231386075551458
73 ms 167.235.130.180
8 2026-08-24 03:09 639231376208713791
68 ms 167.235.130.180
7 2026-08-24 02:52 639231366170589276
67 ms 167.235.130.180
6 2026-08-24 01:59 639231334732159368
46 ms 167.235.130.180
5 2026-08-24 01:43 639231325035670078
5 ms 167.235.130.180
4 2026-08-24 01:27 639231315132253837
2010 ms 167.235.130.180
3 2026-08-24 01:10 639231305014280808
3 ms 167.235.130.180
2 2026-08-24 00:18 639231273779380675
3 ms 167.235.130.180
1 2026-08-24 00:02 639231264180839154
5 ms 167.235.130.180