Apideck experienced a minor incident on September 1, 2025 affecting Logs, lasting 2h 59m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 01, 2025, 07:41 PM UTC
We're currently investigating a report issue where the log view in the admin is displaying an incomplete result set.
- identified Sep 01, 2025, 09:52 PM UTC
The issue has been identified and fix is being implemented.
- monitoring Sep 01, 2025, 10:28 PM UTC
Fix released and we're monitoring results.
- resolved Sep 01, 2025, 10:40 PM UTC
This incident has been resolved
- postmortem Sep 02, 2025, 07:55 AM UTC
## Request Logging Service - Resolved **Incident Period:** August 28, 2025, 2:00 PM GMT\+2 to September 2, 2025, 12:30 AM GMT\+2 ## Impact Summary During this period, logging of incoming API requests to Unify was intermittent. While downstream connector requests \(calls made to third-party services on your behalf\) continued to be logged normally, some primary API requests made directly to Unify endpoints were not captured in our logging system. ## What Was Affected * **Intermittent logging** of incoming requests to Unify API endpoints \(e.g., `/crm/contacts`, `/accounting/invoices`\) * Request logs available through the Unify dashboard and API may show incomplete request history for this period * Downstream connector activity \(requests to Salesforce, HubSpot, Xero, etc.\) remained fully logged throughout ## What Was NOT Affected * **API functionality** - All API requests continued to process normally * **Downstream connector logging** - Complete visibility into third-party service interactions was maintained * **Service reliability** - No impact on API performance or availability * **Billing accuracy** - Usage tracking and billing calculations were unaffected ## Resolution The issue has been fully resolved as of approximately midnight September 2, 2025. All request logging is now functioning normally, with complete visibility into both incoming API requests and downstream connector activity. ## Next Steps If you require historical request data from the affected period, please contact our support team at [[email protected]](mailto:[email protected]).