DNS response history for ns2.triohost.com

ns2.triohost.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 36 DNS check records, 36 successful responses, 0 failed responses, and 252 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.triohost.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

252 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

150.136.41.32

Most recently resolved hosting IP on selected date

Successful Responses

36

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.triohost.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
36 2026-08-25 12:34 639232576780683689
220 ms 150.136.41.32
35 2026-08-25 12:17 639232566381512620
17 ms 150.136.41.32
34 2026-08-25 12:00 639232556111768563
126 ms 150.136.41.32
33 2026-08-25 11:43 639232545839529039
103 ms 150.136.41.32
32 2026-08-25 11:25 639232535349285207
99 ms 150.136.41.32
31 2026-08-25 11:08 639232524938080723
214 ms 150.136.41.32
30 2026-08-25 10:14 639232492740373468
222 ms 150.136.41.32
29 2026-08-25 09:57 639232482235303141
226 ms 150.136.41.32
28 2026-08-25 09:39 639232471861770303
99 ms 150.136.41.32
27 2026-08-25 09:22 639232461630217327
2118 ms 150.136.41.32
26 2026-08-25 09:05 639232451282965990
104 ms 150.136.41.32
25 2026-08-25 08:48 639232440814614938
128 ms 150.136.41.32
24 2026-08-25 08:30 639232430410720425
120 ms 150.136.41.32
23 2026-08-25 08:13 639232420003096185
237 ms 150.136.41.32
22 2026-08-25 07:55 639232409467287444
214 ms 150.136.41.32
21 2026-08-25 07:38 639232399077195997
235 ms 150.136.41.32
20 2026-08-25 07:21 639232388731528337
106 ms 150.136.41.32
19 2026-08-25 07:03 639232378288598612
208 ms 150.136.41.32
18 2026-08-25 06:10 639232346196373643
110 ms 150.136.41.32
17 2026-08-25 05:53 639232336112370741
2098 ms 150.136.41.32
16 2026-08-25 05:36 639232326146508970
219 ms 150.136.41.32
15 2026-08-25 05:20 639232316189381720
3 ms 150.136.41.32
14 2026-08-25 05:03 639232306217998913
5 ms 150.136.41.32
13 2026-08-25 04:47 639232296255744174
214 ms 150.136.41.32
12 2026-08-25 04:30 639232286095760789
232 ms 150.136.41.32
11 2026-08-25 04:13 639232276086186273
248 ms 150.136.41.32
10 2026-08-25 03:56 639232265900986425
128 ms 150.136.41.32
9 2026-08-25 03:39 639232255723518075
117 ms 150.136.41.32
8 2026-08-25 03:22 639232245484452890
42 ms 150.136.41.32
7 2026-08-25 03:05 639232235157175331
11 ms 150.136.41.32
6 2026-08-25 02:11 639232203197189095
216 ms 150.136.41.32
5 2026-08-25 01:54 639232192844564298
24 ms 150.136.41.32
4 2026-08-25 01:37 639232182496008942
206 ms 150.136.41.32
3 2026-08-25 01:20 639232172197053132
161 ms 150.136.41.32
2 2026-08-25 00:26 639232140250307418
211 ms 150.136.41.32
1 2026-08-25 00:09 639232129927860324
43 ms 150.136.41.32