DNS response history for ns2.triactiva.net

ns2.triactiva.net 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 33 DNS check records, 33 successful responses, 0 failed responses, and 517 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.triactiva.net.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

517 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

190.3.169.39

Most recently resolved hosting IP on selected date

Successful Responses

33

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.triactiva.net

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
33 2026-08-25 11:50 639232545839529039
443 ms 190.3.169.39
32 2026-08-25 11:33 639232535349285207
868 ms 190.3.169.39
31 2026-08-25 11:15 639232524938080723
435 ms 190.3.169.39
30 2026-08-25 10:21 639232492740373468
876 ms 190.3.169.39
29 2026-08-25 10:04 639232482235303141
879 ms 190.3.169.39
28 2026-08-25 09:47 639232471861770303
436 ms 190.3.169.39
27 2026-08-25 09:29 639232461630217327
441 ms 190.3.169.39
26 2026-08-25 09:12 639232451282965990
437 ms 190.3.169.39
25 2026-08-25 08:55 639232440814614938
450 ms 190.3.169.39
24 2026-08-25 08:38 639232430410720425
467 ms 190.3.169.39
23 2026-08-25 08:20 639232420003096185
442 ms 190.3.169.39
22 2026-08-25 08:03 639232409467287444
437 ms 190.3.169.39
21 2026-08-25 07:45 639232399077195997
878 ms 190.3.169.39
20 2026-08-25 07:28 639232388731528337
433 ms 190.3.169.39
19 2026-08-25 07:11 639232378288598612
868 ms 190.3.169.39
18 2026-08-25 06:17 639232346196373643
436 ms 190.3.169.39
17 2026-08-25 06:00 639232336112370741
869 ms 190.3.169.39
16 2026-08-25 05:43 639232326146508970
3 ms 190.3.169.39
15 2026-08-25 05:27 639232316189381720
874 ms 190.3.169.39
14 2026-08-25 05:10 639232306217998913
4 ms 190.3.169.39
13 2026-08-25 04:54 639232296255744174
2 ms 190.3.169.39
12 2026-08-25 04:37 639232286095760789
869 ms 190.3.169.39
11 2026-08-25 04:20 639232276086186273
439 ms 190.3.169.39
10 2026-08-25 04:03 639232265900986425
433 ms 190.3.169.39
9 2026-08-25 03:46 639232255723518075
434 ms 190.3.169.39
8 2026-08-25 03:29 639232245484452890
868 ms 190.3.169.39
7 2026-08-25 03:12 639232235157175331
3 ms 190.3.169.39
6 2026-08-25 02:19 639232203197189095
2 ms 190.3.169.39
5 2026-08-25 02:02 639232192844564298
432 ms 190.3.169.39
4 2026-08-25 01:44 639232182496008942
432 ms 190.3.169.39
3 2026-08-25 01:27 639232172197053132
872 ms 190.3.169.39
2 2026-08-25 00:34 639232140250307418
429 ms 190.3.169.39
1 2026-08-25 00:17 639232129927860324
869 ms 190.3.169.39