DNS response history for ns2.tridalwave.com

ns2.tridalwave.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-27. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 104 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.tridalwave.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

104 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

144.76.18.104

Most recently resolved hosting IP on selected date

Successful Responses

27

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.tridalwave.com

Showing DNS history for 2026-08-27 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
27 2026-08-27 08:50 639234170713214496
26 ms 144.76.18.104
26 2026-08-27 08:33 639234160341037652
14 ms 144.76.18.104
25 2026-08-27 08:16 639234149799404224
13 ms 144.76.18.104
24 2026-08-27 07:58 639234139553286469
16 ms 144.76.18.104
23 2026-08-27 07:05 639234107183588293
39 ms 144.76.18.104
22 2026-08-27 06:47 639234096905435724
13 ms 144.76.18.104
21 2026-08-27 06:30 639234086579410775
36 ms 144.76.18.104
20 2026-08-27 06:13 639234076291157956
43 ms 144.76.18.104
19 2026-08-27 05:56 639234065981939454
20 ms 144.76.18.104
18 2026-08-27 05:39 639234055548642997
8 ms 144.76.18.104
17 2026-08-27 05:21 639234045267979603
9 ms 144.76.18.104
16 2026-08-27 05:04 639234034999717463
31 ms 144.76.18.104
15 2026-08-27 04:47 639234024739225358
15 ms 144.76.18.104
14 2026-08-27 04:30 639234014311170162
41 ms 144.76.18.104
13 2026-08-27 04:12 639234003806017640
86 ms 144.76.18.104
12 2026-08-27 03:55 639233993356203030
44 ms 144.76.18.104
11 2026-08-27 03:02 639233961301716608
29 ms 144.76.18.104
10 2026-08-27 02:44 639233950834200647
2021 ms 144.76.18.104
9 2026-08-27 02:27 639233940431849026
41 ms 144.76.18.104
8 2026-08-27 02:10 639233930110596398
138 ms 144.76.18.104
7 2026-08-27 01:52 639233919705434540
7 ms 144.76.18.104
6 2026-08-27 01:35 639233909452807845
24 ms 144.76.18.104
5 2026-08-27 01:18 639233899096420820
26 ms 144.76.18.104
4 2026-08-27 01:01 639233888707824939
10 ms 144.76.18.104
3 2026-08-27 00:43 639233878461203802
9 ms 144.76.18.104
2 2026-08-27 00:26 639233868060868209
27 ms 144.76.18.104
1 2026-08-27 00:08 639233857450922991
19 ms 144.76.18.104