DNS response history for ns2.msharch.com

ns2.msharch.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-31. For this date, NameServerHistory found 37 DNS check records, 36 successful responses, 1 failed responses, and 222 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.msharch.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

222 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-31 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.99.141.127

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

Showing DNS history for 2026-08-31 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-31 12:11 639237742927117371
220 ms 192.99.141.127
36 2026-08-31 11:54 639237732538256235
231 ms 192.99.141.127
35 2026-08-31 11:37 639237722025682013
218 ms 192.99.141.127
34 2026-08-31 11:19 639237711568720101
217 ms 192.99.141.127
33 2026-08-31 11:02 639237701119461876
218 ms 192.99.141.127
32 2026-08-31 10:44 639237690759595513
-
31 2026-08-31 10:27 639237680122296836
217 ms 192.99.141.127
30 2026-08-31 09:33 639237647999458954
212 ms 192.99.141.127
29 2026-08-31 09:16 639237637680951774
221 ms 192.99.141.127
28 2026-08-31 08:59 639237627437728712
5 ms 192.99.141.127
27 2026-08-31 08:42 639237617127808241
220 ms 192.99.141.127
26 2026-08-31 08:24 639237606990101394
4 ms 192.99.141.127
25 2026-08-31 08:08 639237596595480036
227 ms 192.99.141.127
24 2026-08-31 07:50 639237586261012001
215 ms 192.99.141.127
23 2026-08-31 07:33 639237576047657695
226 ms 192.99.141.127
22 2026-08-31 07:16 639237565832936443
215 ms 192.99.141.127
21 2026-08-31 06:59 639237555466329546
3 ms 192.99.141.127
20 2026-08-31 06:42 639237545032411072
215 ms 192.99.141.127
19 2026-08-31 06:24 639237534469438634
3 ms 192.99.141.127
18 2026-08-31 05:30 639237502279296801
219 ms 192.99.141.127
17 2026-08-31 05:13 639237492362730124
219 ms 192.99.141.127
16 2026-08-31 04:57 639237482311584319
3 ms 192.99.141.127
15 2026-08-31 04:40 639237472150685594
228 ms 192.99.141.127
14 2026-08-31 04:23 639237462055295430
110 ms 192.99.141.127
13 2026-08-31 04:06 639237452089913890
211 ms 192.99.141.127
12 2026-08-31 03:50 639237441972654103
218 ms 192.99.141.127
11 2026-08-31 03:33 639237432052396478
218 ms 192.99.141.127
10 2026-08-31 03:16 639237422012990851
215 ms 192.99.141.127
9 2026-08-31 02:59 639237411889602012
212 ms 192.99.141.127
8 2026-08-31 02:42 639237401637354221
109 ms 192.99.141.127
7 2026-08-31 02:25 639237391412690360
218 ms 192.99.141.127
6 2026-08-31 01:33 639237359972957132
218 ms 192.99.141.127
5 2026-08-31 01:16 639237350032183979
222 ms 192.99.141.127
4 2026-08-31 01:00 639237340111452066
219 ms 192.99.141.127
3 2026-08-31 00:43 639237329967272514
213 ms 192.99.141.127
2 2026-08-31 00:26 639237319916508151
1638 ms 192.99.141.127
1 2026-08-31 00:09 639237309944877243
222 ms 192.99.141.127