Apideck Outage History
Apideck is up right nowPingoru has recorded 49 incidents for Apideck: 2 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 6 of 720 (1%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 3 of 720 (0%) |
| October 2026 | 0 | 0 of 514 (0%) |
Incidents, newest first
Notice September 15, 2026 Delayed log delivery 2h 39m Logs
Started Sep 15, 2026, 08:53 AM UTC· resolved Sep 15, 2026, 11:33 AM UTC
- investigating Sep 15, 2026, 08:53 AM UTC
Request Logs and Webhook Logs in the dashboard are not displaying recent entries. We have identified the cause and are working on a fix. API traffic is not affected. Requests, webhooks and all Unify endpoints continue to operate normally — this affects log visibility in the dashboard only.
- monitoring Sep 15, 2026, 09:13 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 15, 2026, 11:33 AM UTC
This incident has been resolved.
Minor April 20, 2026 Vercel Security Incident Response 5h 51m Ecosystems, Developer docs, Web application, Cloud catalog
Started Apr 20, 2026, 07:40 AM UTC· resolved Apr 20, 2026, 01:31 PM UTC
- investigating Apr 20, 2026, 07:40 AM UTC
While there is no evidence Apideck systems have been affected by the Vercel breach, we are rotating all sensitive keys to ensure the protection of our applications hosted with Vercel.
- resolved Apr 20, 2026, 01:31 PM UTC
All vercel hosted credentials have been rotated across Apideck application
Minor September 1, 2025 Request Logs: Incomplete Results 2h 59m Logs
Started Sep 01, 2025, 07:41 PM UTC· resolved Sep 01, 2025, 10:40 PM UTC
- 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]).
Notice July 1, 2025 Automated Refresh Token Warmer Failures 12d 15h Vault API
Started Jul 01, 2025, 07:50 AM UTC· resolved Jul 13, 2025, 11:09 PM UTC
- monitoring Jul 01, 2025, 07:50 AM UTC
We identified an issue with the automated system responsible for refreshing tokens, which caused some tokens to expire unexpectedly. We’ve implemented changes to improve the system’s resilience under back-pressure and are actively monitoring to ensure this does not recur.
- resolved Jul 13, 2025, 11:09 PM UTC
This incident has been resolved.
Minor May 14, 2025 Logs Processing System Degradation 41m Logs
Started May 14, 2025, 06:07 PM UTC· resolved May 14, 2025, 06:48 PM UTC
- investigating May 14, 2025, 06:07 PM UTC
We are currently experiencing an issue with our Logs processing system since May 14, 2025 at approximately 16:18 UTC. New logs are not being properly processed at this time. Impact: - New logs are not being processed into our analytics system - Historical logs remain accessible - Reading logs through your admin Portal is not impacted Our engineering team is actively working to resolve this issue. We will provide updates as we make progress toward resolution. We apologize for any inconvenience this may cause and appreciate your patience.
- resolved May 14, 2025, 06:48 PM UTC
This incident has been resolved.
Minor March 4, 2025 Delays in webhook event processing with connectors that utilize Virtual Webhooks 1d Webhooks
Started Mar 04, 2025, 07:44 AM UTC· resolved Mar 05, 2025, 08:23 AM UTC
- investigating Mar 04, 2025, 07:44 AM UTC
We are currently investigating this issue.
- resolved Mar 05, 2025, 08:23 AM UTC
This incident has been resolved.
- postmortem Mar 06, 2025, 08:26 PM UTC
Last week, we identified an issue in our system that led to delays in webhook event processing and manual sync triggers. A backlog of messages accumulated in our processing queue, causing high resource utilization and degraded performance. **Root Cause** The issue was traced to a bug in our pagination logic when processing data. This caused an unexpected loop, leading to repeated processing attempts and message buildup in our queue. **Resolution** We implemented a series of fixes, including: * Correcting the pagination logic to prevent looping * Optimizing message processing and error handling * Enhancing system monitoring to detect similar issues earlier **Impact** During the incident, some customers experienced delays in receiving webhook events and manually triggering syncs. We have since resolved the issue and taken steps to prevent recurrence. **Next Steps** We are implementing additional monitoring and safeguards to improve system resilience and ensure seamless webhook processing. We appreciate your patience and remain committed to maintaining a reliable experience.