DNS response history for ns2.tricommconstruct.com

ns2.tricommconstruct.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 483 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.tricommconstruct.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

483 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.79.16.190

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.tricommconstruct.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:58 639232482235303141
144 ms 45.79.16.190
28 2026-08-25 09:40 639232471861770303
4135 ms 45.79.16.190
27 2026-08-25 09:23 639232461630217327
137 ms 45.79.16.190
26 2026-08-25 09:06 639232451282965990
139 ms 45.79.16.190
25 2026-08-25 08:48 639232440814614938
133 ms 45.79.16.190
24 2026-08-25 08:31 639232430410720425
2142 ms 45.79.16.190
23 2026-08-25 08:14 639232420003096185
2136 ms 45.79.16.190
22 2026-08-25 07:56 639232409467287444
157 ms 45.79.16.190
21 2026-08-25 07:39 639232399077195997
145 ms 45.79.16.190
20 2026-08-25 07:22 639232388731528337
153 ms 45.79.16.190
19 2026-08-25 07:04 639232378288598612
141 ms 45.79.16.190
18 2026-08-25 06:11 639232346196373643
143 ms 45.79.16.190
17 2026-08-25 05:54 639232336112370741
11 ms 45.79.16.190
16 2026-08-25 05:37 639232326146508970
140 ms 45.79.16.190
15 2026-08-25 05:21 639232316189381720
148 ms 45.79.16.190
14 2026-08-25 05:04 639232306217998913
152 ms 45.79.16.190
13 2026-08-25 04:48 639232296255744174
131 ms 45.79.16.190
12 2026-08-25 04:31 639232286095760789
140 ms 45.79.16.190
11 2026-08-25 04:14 639232276086186273
131 ms 45.79.16.190
10 2026-08-25 03:57 639232265900986425
127 ms 45.79.16.190
9 2026-08-25 03:40 639232255723518075
169 ms 45.79.16.190
8 2026-08-25 03:23 639232245484452890
166 ms 45.79.16.190
7 2026-08-25 03:06 639232235157175331
131 ms 45.79.16.190
6 2026-08-25 02:12 639232203197189095
129 ms 45.79.16.190
5 2026-08-25 01:55 639232192844564298
134 ms 45.79.16.190
4 2026-08-25 01:38 639232182496008942
131 ms 45.79.16.190
3 2026-08-25 01:21 639232172197053132
133 ms 45.79.16.190
2 2026-08-25 00:27 639232140250307418
2178 ms 45.79.16.190
1 2026-08-25 00:10 639232129927860324
143 ms 45.79.16.190