DNS response history for ns2.triplesystems.com

ns2.triplesystems.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 422 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.triplesystems.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

422 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.19.246.134

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.triplesystems.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 09:47 639232471861770303
416 ms 61.19.246.134
28 2026-08-25 09:30 639232461630217327
1018 ms 61.19.246.134
27 2026-08-25 09:13 639232451282965990
430 ms 61.19.246.134
26 2026-08-25 08:55 639232440814614938
426 ms 61.19.246.134
25 2026-08-25 08:38 639232430410720425
399 ms 61.19.246.134
24 2026-08-25 08:21 639232420003096185
1002 ms 61.19.246.134
23 2026-08-25 08:03 639232409467287444
1570 ms 61.19.246.134
22 2026-08-25 07:46 639232399077195997
406 ms 61.19.246.134
21 2026-08-25 07:28 639232388731528337
412 ms 61.19.246.134
20 2026-08-25 07:11 639232378288598612
425 ms 61.19.246.134
19 2026-08-25 06:17 639232346196373643
395 ms 61.19.246.134
18 2026-08-25 06:00 639232336112370741
413 ms 61.19.246.134
17 2026-08-25 05:44 639232326146508970
411 ms 61.19.246.134
16 2026-08-25 05:27 639232316189381720
395 ms 61.19.246.134
15 2026-08-25 05:11 639232306217998913
399 ms 61.19.246.134
14 2026-08-25 04:54 639232296255744174
4 ms 61.19.246.134
13 2026-08-25 04:37 639232286095760789
17 ms 61.19.246.134
12 2026-08-25 04:20 639232276086186273
4 ms 61.19.246.134
11 2026-08-25 04:04 639232265900986425
4 ms 61.19.246.134
10 2026-08-25 03:47 639232255723518075
410 ms 61.19.246.134
9 2026-08-25 03:30 639232245484452890
382 ms 61.19.246.134
8 2026-08-25 03:12 639232235157175331
396 ms 61.19.246.134
7 2026-08-25 02:19 639232203197189095
397 ms 61.19.246.134
6 2026-08-25 02:02 639232192844564298
410 ms 61.19.246.134
5 2026-08-25 01:45 639232182496008942
2 ms 61.19.246.134
4 2026-08-25 01:27 639232172197053132
422 ms 61.19.246.134
3 2026-08-25 00:34 639232140250307418
429 ms 61.19.246.134
2 2026-08-25 00:17 639232129927860324
417 ms 61.19.246.134
1 2026-08-25 00:00 639232119551972438
415 ms 61.19.246.134