DNS response history for ns2.multilinestreasury.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

306 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

159.198.36.158

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

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
30 2026-08-26 09:36 639233329214918079
323 ms 159.198.36.158
29 2026-08-26 09:19 639233318749762337
314 ms 159.198.36.158
28 2026-08-26 09:02 639233308387917838
301 ms 159.198.36.158
27 2026-08-26 08:44 639233297961740122
303 ms 159.198.36.158
26 2026-08-26 08:27 639233287487159094
303 ms 159.198.36.158
25 2026-08-26 08:10 639233276995531707
317 ms 159.198.36.158
24 2026-08-26 07:52 639233266521568229
282 ms 159.198.36.158
23 2026-08-26 07:35 639233256081047431
293 ms 159.198.36.158
22 2026-08-26 06:41 639233223620132921
306 ms 159.198.36.158
21 2026-08-26 06:23 639233213287814244
313 ms 159.198.36.158
20 2026-08-26 06:06 639233202925983161
309 ms 159.198.36.158
19 2026-08-26 05:49 639233192644780696
321 ms 159.198.36.158
18 2026-08-26 05:32 639233182401183833
317 ms 159.198.36.158
17 2026-08-26 05:15 639233172074181051
292 ms 159.198.36.158
16 2026-08-26 04:57 639233161808421455
307 ms 159.198.36.158
15 2026-08-26 04:40 639233151357344052
312 ms 159.198.36.158
14 2026-08-26 04:23 639233141034116946
290 ms 159.198.36.158
13 2026-08-26 04:06 639233130828334142
307 ms 159.198.36.158
12 2026-08-26 03:49 639233120373450007
312 ms 159.198.36.158
11 2026-08-26 03:31 639233110066216193
304 ms 159.198.36.158
10 2026-08-26 02:38 639233078065410564
300 ms 159.198.36.158
9 2026-08-26 02:21 639233067787457832
287 ms 159.198.36.158
8 2026-08-26 02:04 639233057501801162
314 ms 159.198.36.158
7 2026-08-26 01:46 639233047089431703
310 ms 159.198.36.158
6 2026-08-26 01:29 639233036754790688
313 ms 159.198.36.158
5 2026-08-26 01:12 639233026412602472
297 ms 159.198.36.158
4 2026-08-26 00:55 639233016064066127
314 ms 159.198.36.158
3 2026-08-26 00:37 639233005922655772
307 ms 159.198.36.158
2 2026-08-26 00:20 639232995672256907
318 ms 159.198.36.158
1 2026-08-26 00:03 639232985300872416
292 ms 159.198.36.158