DNS response history for ns1.trinitycorp.com

ns1.trinitycorp.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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 463 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.trinitycorp.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

463 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.1.60.244

Most recently resolved hosting IP on selected date

Successful Responses

35

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.trinitycorp.com

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:16 639234253963286387
375 ms 210.1.60.244
34 2026-08-27 10:58 639234243654907465
384 ms 210.1.60.244
33 2026-08-27 10:41 639234233269654413
377 ms 210.1.60.244
32 2026-08-27 10:24 639234222943951923
374 ms 210.1.60.244
31 2026-08-27 10:07 639234212558002823
206 ms 210.1.60.244
30 2026-08-27 09:49 639234202117531850
375 ms 210.1.60.244
29 2026-08-27 09:32 639234191649612722
375 ms 210.1.60.244
28 2026-08-27 09:14 639234181105879568
379 ms 210.1.60.244
27 2026-08-27 08:57 639234170713214496
372 ms 210.1.60.244
26 2026-08-27 08:40 639234160341037652
370 ms 210.1.60.244
25 2026-08-27 08:22 639234149799404224
381 ms 210.1.60.244
24 2026-08-27 08:05 639234139553286469
375 ms 210.1.60.244
23 2026-08-27 07:11 639234107183588293
369 ms 210.1.60.244
22 2026-08-27 06:54 639234096905435724
2195 ms 210.1.60.244
21 2026-08-27 06:37 639234086579410775
399 ms 210.1.60.244
20 2026-08-27 06:19 639234076291157956
368 ms 210.1.60.244
19 2026-08-27 06:02 639234065981939454
373 ms 210.1.60.244
18 2026-08-27 05:45 639234055548642997
369 ms 210.1.60.244
17 2026-08-27 05:28 639234045267979603
199 ms 210.1.60.244
16 2026-08-27 05:11 639234034999717463
2208 ms 210.1.60.244
15 2026-08-27 04:54 639234024739225358
368 ms 210.1.60.244
14 2026-08-27 04:36 639234014311170162
374 ms 210.1.60.244
13 2026-08-27 04:19 639234003806017640
376 ms 210.1.60.244
12 2026-08-27 04:01 639233993356203030
368 ms 210.1.60.244
11 2026-08-27 03:08 639233961301716608
366 ms 210.1.60.244
10 2026-08-27 02:51 639233950834200647
368 ms 210.1.60.244
9 2026-08-27 02:33 639233940431849026
367 ms 210.1.60.244
8 2026-08-27 02:16 639233930110596398
371 ms 210.1.60.244
7 2026-08-27 01:59 639233919705434540
371 ms 210.1.60.244
6 2026-08-27 01:42 639233909452807845
192 ms 210.1.60.244
5 2026-08-27 01:24 639233899096420820
370 ms 210.1.60.244
4 2026-08-27 01:07 639233888707824939
381 ms 210.1.60.244
3 2026-08-27 00:50 639233878461203802
371 ms 210.1.60.244
2 2026-08-27 00:33 639233868060868209
370 ms 210.1.60.244
1 2026-08-27 00:15 639233857450922991
380 ms 210.1.60.244