DNS response history for ns4.monoassault.com

ns4.monoassault.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-25. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 165 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 ns4.monoassault.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

165 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

38.123.149.15

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns4.monoassault.com

Showing DNS history for 2026-08-25 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
33 2026-08-25 11:47 639232545839529039
132 ms 38.123.149.15
32 2026-08-25 11:29 639232535349285207
97 ms 38.123.149.15
31 2026-08-25 11:12 639232524938080723
215 ms 38.123.149.15
30 2026-08-25 10:18 639232492740373468
244 ms 38.123.149.15
29 2026-08-25 10:01 639232482235303141
247 ms 38.123.149.15
28 2026-08-25 09:44 639232471861770303
204 ms 38.123.149.15
27 2026-08-25 09:26 639232461630217327
110 ms 38.123.149.15
26 2026-08-25 09:09 639232451282965990
237 ms 38.123.149.15
25 2026-08-25 08:52 639232440814614938
239 ms 38.123.149.15
24 2026-08-25 08:34 639232430410720425
243 ms 38.123.149.15
23 2026-08-25 08:17 639232420003096185
243 ms 38.123.149.15
22 2026-08-25 08:00 639232409467287444
139 ms 38.123.149.15
21 2026-08-25 07:42 639232399077195997
247 ms 38.123.149.15
20 2026-08-25 07:25 639232388731528337
129 ms 38.123.149.15
19 2026-08-25 07:08 639232378288598612
250 ms 38.123.149.15
18 2026-08-25 06:14 639232346196373643
3 ms 38.123.149.15
17 2026-08-25 05:57 639232336112370741
131 ms 38.123.149.15
16 2026-08-25 05:41 639232326146508970
135 ms 38.123.149.15
15 2026-08-25 05:24 639232316189381720
240 ms 38.123.149.15
14 2026-08-25 05:07 639232306217998913
233 ms 38.123.149.15
13 2026-08-25 04:51 639232296255744174
235 ms 38.123.149.15
12 2026-08-25 04:34 639232286095760789
103 ms 38.123.149.15
11 2026-08-25 04:17 639232276086186273
7 ms 38.123.149.15
10 2026-08-25 04:00 639232265900986425
149 ms 38.123.149.15
9 2026-08-25 03:43 639232255723518075
3 ms 38.123.149.15
8 2026-08-25 03:26 639232245484452890
234 ms 38.123.149.15
7 2026-08-25 03:09 639232235157175331
241 ms 38.123.149.15
6 2026-08-25 02:16 639232203197189095
239 ms 38.123.149.15
5 2026-08-25 01:59 639232192844564298
103 ms 38.123.149.15
4 2026-08-25 01:41 639232182496008942
147 ms 38.123.149.15
3 2026-08-25 01:24 639232172197053132
240 ms 38.123.149.15
2 2026-08-25 00:31 639232140250307418
4 ms 38.123.149.15
1 2026-08-25 00:14 639232129927860324
19 ms 38.123.149.15