DNS response history for ns2.triocup.com

ns2.triocup.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 129 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.triocup.com.
Records on Selected Date

23

Historical checks stored for this nameserver on selected date

Average Latency

129 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 08:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.23.86.159

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.triocup.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:08 639232420003096185
34 ms 94.23.86.159
22 2026-08-25 07:51 639232409467287444
47 ms 94.23.86.159
21 2026-08-25 07:33 639232399077195997
46 ms 94.23.86.159
20 2026-08-25 07:16 639232388731528337
64 ms 94.23.86.159
19 2026-08-25 06:59 639232378288598612
38 ms 94.23.86.159
18 2026-08-25 06:05 639232346196373643
72 ms 94.23.86.159
17 2026-08-25 05:48 639232336112370741
53 ms 94.23.86.159
16 2026-08-25 05:32 639232326146508970
8 ms 94.23.86.159
15 2026-08-25 05:15 639232316189381720
31 ms 94.23.86.159
14 2026-08-25 04:59 639232306217998913
2025 ms 94.23.86.159
13 2026-08-25 04:42 639232296255744174
58 ms 94.23.86.159
12 2026-08-25 04:25 639232286095760789
57 ms 94.23.86.159
11 2026-08-25 04:08 639232276086186273
34 ms 94.23.86.159
10 2026-08-25 03:51 639232265900986425
88 ms 94.23.86.159
9 2026-08-25 03:34 639232255723518075
17 ms 94.23.86.159
8 2026-08-25 03:17 639232245484452890
33 ms 94.23.86.159
7 2026-08-25 03:00 639232235157175331
37 ms 94.23.86.159
6 2026-08-25 02:07 639232203197189095
77 ms 94.23.86.159
5 2026-08-25 01:50 639232192844564298
24 ms 94.23.86.159
4 2026-08-25 01:32 639232182496008942
13 ms 94.23.86.159
3 2026-08-25 01:15 639232172197053132
37 ms 94.23.86.159
2 2026-08-25 00:22 639232140250307418
52 ms 94.23.86.159
1 2026-08-25 00:05 639232129927860324
31 ms 94.23.86.159