DNS response history for ns2.tripex.net

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

23

Historical checks stored for this nameserver on selected date

Average Latency

236 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 08:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

178.63.253.188

Most recently resolved hosting IP on selected date

Successful Responses

23

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.tripex.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
23 2026-08-25 08:12 639232420003096185
77 ms 178.63.253.188
22 2026-08-25 07:55 639232409467287444
46 ms 178.63.253.188
21 2026-08-25 07:37 639232399077195997
54 ms 178.63.253.188
20 2026-08-25 07:20 639232388731528337
46 ms 178.63.253.188
19 2026-08-25 07:03 639232378288598612
79 ms 178.63.253.188
18 2026-08-25 06:09 639232346196373643
26 ms 178.63.253.188
17 2026-08-25 05:52 639232336112370741
116 ms 178.63.253.188
16 2026-08-25 05:36 639232326146508970
40 ms 178.63.253.188
15 2026-08-25 05:19 639232316189381720
78 ms 178.63.253.188
14 2026-08-25 05:03 639232306217998913
51 ms 178.63.253.188
13 2026-08-25 04:46 639232296255744174
74 ms 178.63.253.188
12 2026-08-25 04:29 639232286095760789
77 ms 178.63.253.188
11 2026-08-25 04:12 639232276086186273
52 ms 178.63.253.188
10 2026-08-25 03:55 639232265900986425
81 ms 178.63.253.188
9 2026-08-25 03:38 639232255723518075
2033 ms 178.63.253.188
8 2026-08-25 03:21 639232245484452890
39 ms 178.63.253.188
7 2026-08-25 03:04 639232235157175331
58 ms 178.63.253.188
6 2026-08-25 02:11 639232203197189095
143 ms 178.63.253.188
5 2026-08-25 01:54 639232192844564298
49 ms 178.63.253.188
4 2026-08-25 01:36 639232182496008942
2043 ms 178.63.253.188
3 2026-08-25 01:19 639232172197053132
47 ms 178.63.253.188
2 2026-08-25 00:26 639232140250307418
72 ms 178.63.253.188
1 2026-08-25 00:09 639232129927860324
45 ms 178.63.253.188