We identified the issue as a misconfiguration in the read-API endpoint. The fix has been applied, and all call logs should now display correctly. No data was lost.

We have identified an issue in Dashboard → Call Logs that is preventing call records after November 22 (PST) from appearing in the interface.

API access to call logs does not seem affected.