DNS response history for ns2.trinitytech.co.in

ns2.trinitytech.co.in 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 31 DNS check records, 31 successful responses, 0 failed responses, and 559 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.trinitytech.co.in.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

559 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.14.99.172

Most recently resolved hosting IP on selected date

Successful Responses

31

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.trinitytech.co.in

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
31 2026-08-25 11:13 639232524938080723
271 ms 103.14.99.172
30 2026-08-25 10:20 639232492740373468
2454 ms 103.14.99.172
29 2026-08-25 10:03 639232482235303141
260 ms 103.14.99.172
28 2026-08-25 09:45 639232471861770303
252 ms 103.14.99.172
27 2026-08-25 09:28 639232461630217327
258 ms 103.14.99.172
26 2026-08-25 09:11 639232451282965990
254 ms 103.14.99.172
25 2026-08-25 08:53 639232440814614938
265 ms 103.14.99.172
24 2026-08-25 08:36 639232430410720425
9 ms 103.14.99.172
23 2026-08-25 08:19 639232420003096185
565 ms 103.14.99.172
22 2026-08-25 08:01 639232409467287444
259 ms 103.14.99.172
21 2026-08-25 07:44 639232399077195997
246 ms 103.14.99.172
20 2026-08-25 07:26 639232388731528337
401 ms 103.14.99.172
19 2026-08-25 07:09 639232378288598612
809 ms 103.14.99.172
18 2026-08-25 06:15 639232346196373643
8 ms 103.14.99.172
17 2026-08-25 05:58 639232336112370741
939 ms 103.14.99.172
16 2026-08-25 05:42 639232326146508970
288 ms 103.14.99.172
15 2026-08-25 05:25 639232316189381720
4 ms 103.14.99.172
14 2026-08-25 05:09 639232306217998913
242 ms 103.14.99.172
13 2026-08-25 04:52 639232296255744174
250 ms 103.14.99.172
12 2026-08-25 04:35 639232286095760789
350 ms 103.14.99.172
11 2026-08-25 04:18 639232276086186273
258 ms 103.14.99.172
10 2026-08-25 04:02 639232265900986425
780 ms 103.14.99.172
9 2026-08-25 03:45 639232255723518075
347 ms 103.14.99.172
8 2026-08-25 03:28 639232245484452890
259 ms 103.14.99.172
7 2026-08-25 03:10 639232235157175331
2183 ms 103.14.99.172
6 2026-08-25 02:17 639232203197189095
775 ms 103.14.99.172
5 2026-08-25 02:00 639232192844564298
2826 ms 103.14.99.172
4 2026-08-25 01:43 639232182496008942
504 ms 103.14.99.172
3 2026-08-25 01:25 639232172197053132
242 ms 103.14.99.172
2 2026-08-25 00:32 639232140250307418
769 ms 103.14.99.172
1 2026-08-25 00:15 639232129927860324
3 ms 103.14.99.172