DNS response history for ns2.msg.systems

ns2.msg.systems 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 37 DNS check records, 36 successful responses, 1 failed responses, and 341 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.msg.systems.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

341 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

217.160.113.37

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.msg.systems

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
37 2026-08-26 12:23 639233434974187439
31 ms 217.160.113.37
36 2026-08-26 12:05 639233424567558554
33 ms 217.160.113.37
35 2026-08-26 11:48 639233414056832719
108 ms 217.160.113.37
34 2026-08-26 11:30 639233403515141099
2011 ms 217.160.113.37
33 2026-08-26 10:36 639233370841350248
276 ms 217.160.113.37
32 2026-08-26 10:18 639233360361507238
74 ms 217.160.113.37
31 2026-08-26 10:01 639233350067824371
157 ms 217.160.113.37
30 2026-08-26 09:44 639233339545274518
42 ms 217.160.113.37
29 2026-08-26 09:26 639233329214918079
55 ms 217.160.113.37
28 2026-08-26 09:09 639233318749762337
2025 ms 217.160.113.37
27 2026-08-26 08:52 639233308387917838
41 ms 217.160.113.37
26 2026-08-26 08:34 639233297961740122
13 ms 217.160.113.37
25 2026-08-26 08:17 639233287487159094
39 ms 217.160.113.37
24 2026-08-26 08:00 639233276995531707
38 ms 217.160.113.37
23 2026-08-26 07:42 639233266521568229
30 ms 217.160.113.37
22 2026-08-26 07:25 639233256081047431
13 ms 217.160.113.37
21 2026-08-26 06:31 639233223620132921
47 ms 217.160.113.37
20 2026-08-26 06:13 639233213287814244
21 ms 217.160.113.37
19 2026-08-26 05:56 639233202925983161
2022 ms 217.160.113.37
18 2026-08-26 05:39 639233192644780696
61 ms 217.160.113.37
17 2026-08-26 05:22 639233182401183833
38 ms 217.160.113.37
16 2026-08-26 05:05 639233172074181051
91 ms 217.160.113.37
15 2026-08-26 04:48 639233161808421455
34 ms 217.160.113.37
14 2026-08-26 04:30 639233151357344052
27 ms 217.160.113.37
13 2026-08-26 04:13 639233141034116946
49 ms 217.160.113.37
12 2026-08-26 03:56 639233130828334142
25 ms 217.160.113.37
11 2026-08-26 03:39 639233120373450007
2309 ms 217.160.113.37
10 2026-08-26 03:21 639233110066216193
12 ms 217.160.113.37
9 2026-08-26 02:28 639233078065410564
2012 ms 217.160.113.37
8 2026-08-26 02:11 639233067787457832
40 ms 217.160.113.37
7 2026-08-26 01:54 639233057501801162
27 ms 217.160.113.37
6 2026-08-26 01:36 639233047089431703
47 ms 217.160.113.37
5 2026-08-26 01:19 639233036754790688
101 ms 217.160.113.37
4 2026-08-26 01:02 639233026412602472
-
3 2026-08-26 00:45 639233016064066127
40 ms 217.160.113.37
2 2026-08-26 00:28 639233005922655772
276 ms 217.160.113.37
1 2026-08-26 00:11 639232995672256907
13 ms 217.160.113.37