DNS response history for ns2.tribaleffect.com

ns2.tribaleffect.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 27 DNS check records, 26 successful responses, 1 failed responses, and 185 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.tribaleffect.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

185 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.168.0.240

Most recently resolved hosting IP on selected date

Successful Responses

26

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.tribaleffect.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
27 2026-08-25 09:20 639232461630217327
22 ms 192.168.0.240
26 2026-08-25 09:03 639232451282965990
9 ms 192.168.0.240
25 2026-08-25 08:45 639232440814614938
32 ms 192.168.0.240
24 2026-08-25 08:28 639232430410720425
15 ms 192.168.0.240
23 2026-08-25 08:11 639232420003096185
12 ms 192.168.0.240
22 2026-08-25 07:53 639232409467287444
14 ms 192.168.0.240
21 2026-08-25 07:36 639232399077195997
96 ms 192.168.0.240
20 2026-08-25 07:18 639232388731528337
2037 ms 192.168.0.240
19 2026-08-25 07:01 639232378288598612
15 ms 192.168.0.240
18 2026-08-25 06:07 639232346196373643
22 ms 192.168.0.240
17 2026-08-25 05:51 639232336112370741
84 ms 192.168.0.240
16 2026-08-25 05:34 639232326146508970
29 ms 192.168.0.240
15 2026-08-25 05:17 639232316189381720
6 ms 192.168.0.240
14 2026-08-25 05:01 639232306217998913
7 ms 192.168.0.240
13 2026-08-25 04:44 639232296255744174
2042 ms 192.168.0.240
12 2026-08-25 04:27 639232286095760789
13 ms 192.168.0.240
11 2026-08-25 04:11 639232276086186273
39 ms 192.168.0.240
10 2026-08-25 03:54 639232265900986425
51 ms 192.168.0.240
9 2026-08-25 03:37 639232255723518075
29 ms 192.168.0.240
8 2026-08-25 03:20 639232245484452890
48 ms 192.168.0.240
7 2026-08-25 03:02 639232235157175331
-
6 2026-08-25 02:09 639232203197189095
28 ms 192.168.0.240
5 2026-08-25 01:52 639232192844564298
10 ms 192.168.0.240
4 2026-08-25 01:35 639232182496008942
29 ms 192.168.0.240
3 2026-08-25 01:17 639232172197053132
24 ms 192.168.0.240
2 2026-08-25 00:24 639232140250307418
81 ms 192.168.0.240
1 2026-08-25 00:07 639232129927860324
18 ms 192.168.0.240