DNS response history for ns2.trinitytraveltrip.com

ns2.trinitytraveltrip.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 421 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.trinitytraveltrip.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

421 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.171.181.79

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.trinitytraveltrip.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 10:02 639232482235303141
152 ms 103.171.181.79
28 2026-08-25 09:44 639232471861770303
19 ms 103.171.181.79
27 2026-08-25 09:27 639232461630217327
269 ms 103.171.181.79
26 2026-08-25 09:10 639232451282965990
274 ms 103.171.181.79
25 2026-08-25 08:52 639232440814614938
141 ms 103.171.181.79
24 2026-08-25 08:35 639232430410720425
2180 ms 103.171.181.79
23 2026-08-25 08:18 639232420003096185
270 ms 103.171.181.79
22 2026-08-25 08:00 639232409467287444
277 ms 103.171.181.79
21 2026-08-25 07:43 639232399077195997
270 ms 103.171.181.79
20 2026-08-25 07:25 639232388731528337
281 ms 103.171.181.79
19 2026-08-25 07:08 639232378288598612
135 ms 103.171.181.79
18 2026-08-25 06:14 639232346196373643
276 ms 103.171.181.79
17 2026-08-25 05:57 639232336112370741
136 ms 103.171.181.79
16 2026-08-25 05:41 639232326146508970
180 ms 103.171.181.79
15 2026-08-25 05:24 639232316189381720
263 ms 103.171.181.79
14 2026-08-25 05:08 639232306217998913
2261 ms 103.171.181.79
13 2026-08-25 04:51 639232296255744174
3 ms 103.171.181.79
12 2026-08-25 04:34 639232286095760789
280 ms 103.171.181.79
11 2026-08-25 04:17 639232276086186273
257 ms 103.171.181.79
10 2026-08-25 04:01 639232265900986425
274 ms 103.171.181.79
9 2026-08-25 03:44 639232255723518075
147 ms 103.171.181.79
8 2026-08-25 03:27 639232245484452890
498 ms 103.171.181.79
7 2026-08-25 03:09 639232235157175331
311 ms 103.171.181.79
6 2026-08-25 02:16 639232203197189095
164 ms 103.171.181.79
5 2026-08-25 01:59 639232192844564298
12 ms 103.171.181.79
4 2026-08-25 01:42 639232182496008942
178 ms 103.171.181.79
3 2026-08-25 01:24 639232172197053132
2140 ms 103.171.181.79
2 2026-08-25 00:31 639232140250307418
282 ms 103.171.181.79
1 2026-08-25 00:14 639232129927860324
277 ms 103.171.181.79