DNS response history for ns2.trivalley.com

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

19

Historical checks stored for this nameserver on selected date

Average Latency

455 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 07:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.80.124.4

Most recently resolved hosting IP on selected date

Successful Responses

19

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.trivalley.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
19 2026-08-25 07:03 639232378288598612
136 ms 208.80.124.4
18 2026-08-25 06:09 639232346196373643
63 ms 208.80.124.4
17 2026-08-25 05:53 639232336112370741
129 ms 208.80.124.4
16 2026-08-25 05:36 639232326146508970
2014 ms 208.80.124.4
15 2026-08-25 05:19 639232316189381720
3 ms 208.80.124.4
14 2026-08-25 05:03 639232306217998913
528 ms 208.80.124.4
13 2026-08-25 04:46 639232296255744174
145 ms 208.80.124.4
12 2026-08-25 04:29 639232286095760789
2008 ms 208.80.124.4
11 2026-08-25 04:13 639232276086186273
121 ms 208.80.124.4
10 2026-08-25 03:56 639232265900986425
73 ms 208.80.124.4
9 2026-08-25 03:39 639232255723518075
653 ms 208.80.124.4
8 2026-08-25 03:22 639232245484452890
44 ms 208.80.124.4
7 2026-08-25 03:04 639232235157175331
132 ms 208.80.124.4
6 2026-08-25 02:11 639232203197189095
124 ms 208.80.124.4
5 2026-08-25 01:54 639232192844564298
29 ms 208.80.124.4
4 2026-08-25 01:37 639232182496008942
2042 ms 208.80.124.4
3 2026-08-25 01:19 639232172197053132
138 ms 208.80.124.4
2 2026-08-25 00:26 639232140250307418
132 ms 208.80.124.4
1 2026-08-25 00:09 639232129927860324
123 ms 208.80.124.4