DNS response history for ns2.ibox.com.br

ns2.ibox.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-26. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 521 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.ibox.com.br.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

521 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.222.29.109

Most recently resolved hosting IP on selected date

Successful Responses

33

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

Showing DNS history for 2026-08-26 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
33 2026-08-26 10:26 639233360361507238
346 ms 51.222.29.109
32 2026-08-26 10:08 639233350067824371
340 ms 51.222.29.109
31 2026-08-26 09:51 639233339545274518
402 ms 51.222.29.109
30 2026-08-26 09:34 639233329214918079
634 ms 51.222.29.109
29 2026-08-26 09:16 639233318749762337
348 ms 51.222.29.109
28 2026-08-26 08:59 639233308387917838
4 ms 51.222.29.109
27 2026-08-26 08:42 639233297961740122
198 ms 51.222.29.109
26 2026-08-26 08:24 639233287487159094
326 ms 51.222.29.109
25 2026-08-26 08:07 639233276995531707
419 ms 51.222.29.109
24 2026-08-26 07:49 639233266521568229
205 ms 51.222.29.109
23 2026-08-26 07:32 639233256081047431
422 ms 51.222.29.109
22 2026-08-26 06:38 639233223620132921
346 ms 51.222.29.109
21 2026-08-26 06:20 639233213287814244
197 ms 51.222.29.109
20 2026-08-26 06:03 639233202925983161
208 ms 51.222.29.109
19 2026-08-26 05:46 639233192644780696
426 ms 51.222.29.109
18 2026-08-26 05:29 639233182401183833
166 ms 51.222.29.109
17 2026-08-26 05:12 639233172074181051
416 ms 51.222.29.109
16 2026-08-26 04:55 639233161808421455
420 ms 51.222.29.109
15 2026-08-26 04:37 639233151357344052
424 ms 51.222.29.109
14 2026-08-26 04:20 639233141034116946
419 ms 51.222.29.109
13 2026-08-26 04:03 639233130828334142
7 ms 51.222.29.109
12 2026-08-26 03:46 639233120373450007
205 ms 51.222.29.109
11 2026-08-26 03:28 639233110066216193
416 ms 51.222.29.109
10 2026-08-26 02:35 639233078065410564
422 ms 51.222.29.109
9 2026-08-26 02:18 639233067787457832
420 ms 51.222.29.109
8 2026-08-26 02:01 639233057501801162
429 ms 51.222.29.109
7 2026-08-26 01:44 639233047089431703
748 ms 51.222.29.109
6 2026-08-26 01:26 639233036754790688
231 ms 51.222.29.109
5 2026-08-26 01:09 639233026412602472
292 ms 51.222.29.109
4 2026-08-26 00:52 639233016064066127
4249 ms 51.222.29.109
3 2026-08-26 00:35 639233005922655772
2256 ms 51.222.29.109
2 2026-08-26 00:18 639232995672256907
426 ms 51.222.29.109
1 2026-08-26 00:01 639232985300872416
415 ms 51.222.29.109