DNS response history for ns2.cp.onbley.com.br

ns2.cp.onbley.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 24 DNS check records, 24 successful responses, 0 failed responses, and 47 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.cp.onbley.com.br.
Records on Selected Date

24

Historical checks stored for this nameserver on selected date

Average Latency

47 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 08:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

40.160.250.106

Most recently resolved hosting IP on selected date

Successful Responses

24

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.cp.onbley.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
24 2026-08-25 08:27 639232430410720425
26 ms 40.160.250.106
23 2026-08-25 08:10 639232420003096185
31 ms 40.160.250.106
22 2026-08-25 07:53 639232409467287444
55 ms 40.160.250.106
21 2026-08-25 07:35 639232399077195997
17 ms 40.160.250.106
20 2026-08-25 07:18 639232388731528337
5 ms 40.160.250.106
19 2026-08-25 07:01 639232378288598612
35 ms 40.160.250.106
18 2026-08-25 06:07 639232346196373643
180 ms 40.160.250.106
17 2026-08-25 05:50 639232336112370741
33 ms 40.160.250.106
16 2026-08-25 05:34 639232326146508970
35 ms 40.160.250.106
15 2026-08-25 05:17 639232316189381720
24 ms 40.160.250.106
14 2026-08-25 05:01 639232306217998913
204 ms 40.160.250.106
13 2026-08-25 04:44 639232296255744174
6 ms 40.160.250.106
12 2026-08-25 04:27 639232286095760789
28 ms 40.160.250.106
11 2026-08-25 04:10 639232276086186273
40 ms 40.160.250.106
10 2026-08-25 03:53 639232265900986425
74 ms 40.160.250.106
9 2026-08-25 03:36 639232255723518075
19 ms 40.160.250.106
8 2026-08-25 03:19 639232245484452890
12 ms 40.160.250.106
7 2026-08-25 03:02 639232235157175331
78 ms 40.160.250.106
6 2026-08-25 02:09 639232203197189095
46 ms 40.160.250.106
5 2026-08-25 01:52 639232192844564298
22 ms 40.160.250.106
4 2026-08-25 01:34 639232182496008942
40 ms 40.160.250.106
3 2026-08-25 01:17 639232172197053132
16 ms 40.160.250.106
2 2026-08-25 00:24 639232140250307418
25 ms 40.160.250.106
1 2026-08-25 00:07 639232129927860324
70 ms 40.160.250.106