DNS response history for ns2.trifive.com

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

23

Historical checks stored for this nameserver on selected date

Average Latency

301 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 08:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.71.251.203

Most recently resolved hosting IP on selected date

Successful Responses

23

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.trifive.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
23 2026-08-25 08:12 639232420003096185
27 ms 66.71.251.203
22 2026-08-25 07:55 639232409467287444
26 ms 66.71.251.203
21 2026-08-25 07:37 639232399077195997
57 ms 66.71.251.203
20 2026-08-25 07:20 639232388731528337
12 ms 66.71.251.203
19 2026-08-25 07:03 639232378288598612
41 ms 66.71.251.203
18 2026-08-25 06:09 639232346196373643
101 ms 66.71.251.203
17 2026-08-25 05:52 639232336112370741
2053 ms 66.71.251.203
16 2026-08-25 05:36 639232326146508970
44 ms 66.71.251.203
15 2026-08-25 05:19 639232316189381720
94 ms 66.71.251.203
14 2026-08-25 05:03 639232306217998913
32 ms 66.71.251.203
13 2026-08-25 04:46 639232296255744174
36 ms 66.71.251.203
12 2026-08-25 04:29 639232286095760789
43 ms 66.71.251.203
11 2026-08-25 04:12 639232276086186273
2088 ms 66.71.251.203
10 2026-08-25 03:55 639232265900986425
6 ms 66.71.251.203
9 2026-08-25 03:38 639232255723518075
10 ms 66.71.251.203
8 2026-08-25 03:21 639232245484452890
39 ms 66.71.251.203
7 2026-08-25 03:04 639232235157175331
59 ms 66.71.251.203
6 2026-08-25 02:11 639232203197189095
14 ms 66.71.251.203
5 2026-08-25 01:54 639232192844564298
2062 ms 66.71.251.203
4 2026-08-25 01:36 639232182496008942
32 ms 66.71.251.203
3 2026-08-25 01:19 639232172197053132
11 ms 66.71.251.203
2 2026-08-25 00:26 639232140250307418
24 ms 66.71.251.203
1 2026-08-25 00:09 639232129927860324
19 ms 66.71.251.203