DNS response history for ns2.tribocm.com.br

ns2.tribocm.com.br 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 36 DNS check records, 36 successful responses, 0 failed responses, and 394 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.tribocm.com.br.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

394 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.116.87.112

Most recently resolved hosting IP on selected date

Successful Responses

36

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.tribocm.com.br

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
36 2026-08-25 12:39 639232576780683689
322 ms 50.116.87.112
35 2026-08-25 12:21 639232566381512620
482 ms 50.116.87.112
34 2026-08-25 12:04 639232556111768563
311 ms 50.116.87.112
33 2026-08-25 11:47 639232545839529039
298 ms 50.116.87.112
32 2026-08-25 11:30 639232535349285207
229 ms 50.116.87.112
31 2026-08-25 11:12 639232524938080723
201 ms 50.116.87.112
30 2026-08-25 10:18 639232492740373468
320 ms 50.116.87.112
29 2026-08-25 10:01 639232482235303141
306 ms 50.116.87.112
28 2026-08-25 09:44 639232471861770303
291 ms 50.116.87.112
27 2026-08-25 09:27 639232461630217327
2206 ms 50.116.87.112
26 2026-08-25 09:09 639232451282965990
312 ms 50.116.87.112
25 2026-08-25 08:52 639232440814614938
205 ms 50.116.87.112
24 2026-08-25 08:35 639232430410720425
309 ms 50.116.87.112
23 2026-08-25 08:17 639232420003096185
11 ms 50.116.87.112
22 2026-08-25 08:00 639232409467287444
319 ms 50.116.87.112
21 2026-08-25 07:42 639232399077195997
315 ms 50.116.87.112
20 2026-08-25 07:25 639232388731528337
20 ms 50.116.87.112
19 2026-08-25 07:08 639232378288598612
227 ms 50.116.87.112
18 2026-08-25 06:14 639232346196373643
318 ms 50.116.87.112
17 2026-08-25 05:57 639232336112370741
311 ms 50.116.87.112
16 2026-08-25 05:41 639232326146508970
442 ms 50.116.87.112
15 2026-08-25 05:24 639232316189381720
292 ms 50.116.87.112
14 2026-08-25 05:07 639232306217998913
294 ms 50.116.87.112
13 2026-08-25 04:51 639232296255744174
359 ms 50.116.87.112
12 2026-08-25 04:34 639232286095760789
320 ms 50.116.87.112
11 2026-08-25 04:17 639232276086186273
292 ms 50.116.87.112
10 2026-08-25 04:00 639232265900986425
302 ms 50.116.87.112
9 2026-08-25 03:43 639232255723518075
210 ms 50.116.87.112
8 2026-08-25 03:26 639232245484452890
300 ms 50.116.87.112
7 2026-08-25 03:09 639232235157175331
306 ms 50.116.87.112
6 2026-08-25 02:16 639232203197189095
2220 ms 50.116.87.112
5 2026-08-25 01:59 639232192844564298
287 ms 50.116.87.112
4 2026-08-25 01:41 639232182496008942
315 ms 50.116.87.112
3 2026-08-25 01:24 639232172197053132
299 ms 50.116.87.112
2 2026-08-25 00:31 639232140250307418
304 ms 50.116.87.112
1 2026-08-25 00:14 639232129927860324
318 ms 50.116.87.112