DNS response history for ns2.trimixserver.com

ns2.trimixserver.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 29 DNS check records, 29 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.trimixserver.com.
Records on Selected Date

29

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-25 09:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.136.97.111

Most recently resolved hosting IP on selected date

Successful Responses

29

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.trimixserver.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
29 2026-08-25 09:53 639232482235303141
28 ms 185.136.97.111
28 2026-08-25 09:36 639232471861770303
39 ms 185.136.97.111
27 2026-08-25 09:18 639232461630217327
31 ms 185.136.97.111
26 2026-08-25 09:01 639232451282965990
6 ms 185.136.97.111
25 2026-08-25 08:44 639232440814614938
12 ms 185.136.97.111
24 2026-08-25 08:26 639232430410720425
10 ms 185.136.97.111
23 2026-08-25 08:09 639232420003096185
27 ms 185.136.97.111
22 2026-08-25 07:52 639232409467287444
48 ms 185.136.97.111
21 2026-08-25 07:34 639232399077195997
113 ms 185.136.97.111
20 2026-08-25 07:17 639232388731528337
14 ms 185.136.97.111
19 2026-08-25 07:00 639232378288598612
27 ms 185.136.97.111
18 2026-08-25 06:06 639232346196373643
21 ms 185.136.97.111
17 2026-08-25 05:49 639232336112370741
9 ms 185.136.97.111
16 2026-08-25 05:33 639232326146508970
7 ms 185.136.97.111
15 2026-08-25 05:16 639232316189381720
42 ms 185.136.97.111
14 2026-08-25 04:59 639232306217998913
43 ms 185.136.97.111
13 2026-08-25 04:43 639232296255744174
5 ms 185.136.97.111
12 2026-08-25 04:26 639232286095760789
8 ms 185.136.97.111
11 2026-08-25 04:09 639232276086186273
34 ms 185.136.97.111
10 2026-08-25 03:52 639232265900986425
34 ms 185.136.97.111
9 2026-08-25 03:35 639232255723518075
9 ms 185.136.97.111
8 2026-08-25 03:18 639232245484452890
38 ms 185.136.97.111
7 2026-08-25 03:01 639232235157175331
110 ms 185.136.97.111
6 2026-08-25 02:08 639232203197189095
31 ms 185.136.97.111
5 2026-08-25 01:51 639232192844564298
67 ms 185.136.97.111
4 2026-08-25 01:33 639232182496008942
14 ms 185.136.97.111
3 2026-08-25 01:16 639232172197053132
32 ms 185.136.97.111
2 2026-08-25 00:23 639232140250307418
2025 ms 185.136.97.111
1 2026-08-25 00:06 639232129927860324
12 ms 185.136.97.111