DNS response history for ns1.trinity3d.com

ns1.trinity3d.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-26. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 633 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 ns1.trinity3d.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

633 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.161.47.170

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 ns1.trinity3d.com

Showing DNS history for 2026-08-26 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-26 11:55 639233414056832719
282 ms 104.161.47.170
35 2026-08-26 11:37 639233403515141099
288 ms 104.161.47.170
34 2026-08-26 10:42 639233370841350248
145 ms 104.161.47.170
33 2026-08-26 10:25 639233360361507238
2161 ms 104.161.47.170
32 2026-08-26 10:08 639233350067824371
287 ms 104.161.47.170
31 2026-08-26 09:51 639233339545274518
10 ms 104.161.47.170
30 2026-08-26 09:33 639233329214918079
281 ms 104.161.47.170
29 2026-08-26 09:16 639233318749762337
281 ms 104.161.47.170
28 2026-08-26 08:58 639233308387917838
208 ms 104.161.47.170
27 2026-08-26 08:41 639233297961740122
283 ms 104.161.47.170
26 2026-08-26 08:24 639233287487159094
285 ms 104.161.47.170
25 2026-08-26 08:06 639233276995531707
2253 ms 104.161.47.170
24 2026-08-26 07:49 639233266521568229
2007 ms 104.161.47.170
23 2026-08-26 07:31 639233256081047431
280 ms 104.161.47.170
22 2026-08-26 06:37 639233223620132921
278 ms 104.161.47.170
21 2026-08-26 06:20 639233213287814244
141 ms 104.161.47.170
20 2026-08-26 06:03 639233202925983161
9 ms 104.161.47.170
19 2026-08-26 05:45 639233192644780696
279 ms 104.161.47.170
18 2026-08-26 05:28 639233182401183833
280 ms 104.161.47.170
17 2026-08-26 05:11 639233172074181051
141 ms 104.161.47.170
16 2026-08-26 04:54 639233161808421455
284 ms 104.161.47.170
15 2026-08-26 04:37 639233151357344052
179 ms 104.161.47.170
14 2026-08-26 04:19 639233141034116946
283 ms 104.161.47.170
13 2026-08-26 04:02 639233130828334142
2007 ms 104.161.47.170
12 2026-08-26 03:45 639233120373450007
9 ms 104.161.47.170
11 2026-08-26 03:28 639233110066216193
290 ms 104.161.47.170
10 2026-08-26 02:35 639233078065410564
2168 ms 104.161.47.170
9 2026-08-26 02:17 639233067787457832
277 ms 104.161.47.170
8 2026-08-26 02:00 639233057501801162
277 ms 104.161.47.170
7 2026-08-26 01:43 639233047089431703
140 ms 104.161.47.170
6 2026-08-26 01:26 639233036754790688
2158 ms 104.161.47.170
5 2026-08-26 01:09 639233026412602472
279 ms 104.161.47.170
4 2026-08-26 00:51 639233016064066127
168 ms 104.161.47.170
3 2026-08-26 00:34 639233005922655772
168 ms 104.161.47.170
2 2026-08-26 00:17 639232995672256907
3645 ms 104.161.47.170
1 2026-08-26 00:00 639232985300872416
281 ms 104.161.47.170