DNS response history for ns2.tripified.ca

ns2.tripified.ca 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 30 DNS check records, 30 successful responses, 0 failed responses, and 379 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.tripified.ca.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

379 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

190.102.102.66

Most recently resolved hosting IP on selected date

Successful Responses

30

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.tripified.ca

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
30 2026-08-25 10:20 639232492740373468
3 ms 190.102.102.66
29 2026-08-25 10:03 639232482235303141
4 ms 190.102.102.66
28 2026-08-25 09:45 639232471861770303
360 ms 190.102.102.66
27 2026-08-25 09:28 639232461630217327
3 ms 190.102.102.66
26 2026-08-25 09:11 639232451282965990
7 ms 190.102.102.66
25 2026-08-25 08:53 639232440814614938
687 ms 190.102.102.66
24 2026-08-25 08:36 639232430410720425
131 ms 190.102.102.66
23 2026-08-25 08:19 639232420003096185
671 ms 190.102.102.66
22 2026-08-25 08:01 639232409467287444
328 ms 190.102.102.66
21 2026-08-25 07:44 639232399077195997
2007 ms 190.102.102.66
20 2026-08-25 07:26 639232388731528337
661 ms 190.102.102.66
19 2026-08-25 07:09 639232378288598612
2128 ms 190.102.102.66
18 2026-08-25 06:15 639232346196373643
2 ms 190.102.102.66
17 2026-08-25 05:59 639232336112370741
5 ms 190.102.102.66
16 2026-08-25 05:42 639232326146508970
6 ms 190.102.102.66
15 2026-08-25 05:25 639232316189381720
3 ms 190.102.102.66
14 2026-08-25 05:09 639232306217998913
690 ms 190.102.102.66
13 2026-08-25 04:52 639232296255744174
3 ms 190.102.102.66
12 2026-08-25 04:35 639232286095760789
332 ms 190.102.102.66
11 2026-08-25 04:18 639232276086186273
666 ms 190.102.102.66
10 2026-08-25 04:02 639232265900986425
676 ms 190.102.102.66
9 2026-08-25 03:45 639232255723518075
670 ms 190.102.102.66
8 2026-08-25 03:28 639232245484452890
3 ms 190.102.102.66
7 2026-08-25 03:10 639232235157175331
3 ms 190.102.102.66
6 2026-08-25 02:17 639232203197189095
664 ms 190.102.102.66
5 2026-08-25 02:00 639232192844564298
655 ms 190.102.102.66
4 2026-08-25 01:43 639232182496008942
3 ms 190.102.102.66
3 2026-08-25 01:26 639232172197053132
2 ms 190.102.102.66
2 2026-08-25 00:32 639232140250307418
3 ms 190.102.102.66
1 2026-08-25 00:15 639232129927860324
7 ms 190.102.102.66