Apideck Outage History

Apideck is up right now

Apideck had 7 outages in the last 2 years totaling 346h 57m of downtime — averaging 0.3 incidents per month.

There were 7 Apideck outages since October 4, 2024 totaling 346h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.apideck.com

Notice September 15, 2026

Delayed log delivery

Detected by Pingoru
Sep 15, 2026, 08:53 AM UTC
Resolved
Sep 15, 2026, 11:33 AM UTC
Duration
2h 39m
Affected: Logs
Timeline · 3 updates
  1. 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.

  2. monitoring Sep 15, 2026, 09:13 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 15, 2026, 11:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 20, 2026

Vercel Security Incident Response

Detected by Pingoru
Apr 20, 2026, 07:40 AM UTC
Resolved
Apr 20, 2026, 01:31 PM UTC
Duration
5h 51m
Affected: EcosystemsDeveloper docsWeb applicationCloud catalog
Timeline · 2 updates
  1. 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.

  2. resolved Apr 20, 2026, 01:31 PM UTC

    All vercel hosted credentials have been rotated across Apideck application

Read the full incident report →

Notice July 1, 2025

Automated Refresh Token Warmer Failures

Detected by Pingoru
Jul 01, 2025, 07:50 AM UTC
Resolved
Jul 13, 2025, 11:09 PM UTC
Duration
12d 15h
Affected: Vault API
Timeline · 2 updates
  1. 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.

  2. resolved Jul 13, 2025, 11:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 14, 2025

Logs Processing System Degradation

Detected by Pingoru
May 14, 2025, 06:07 PM UTC
Resolved
May 14, 2025, 06:48 PM UTC
Duration
41m
Affected: Logs
Timeline · 2 updates
  1. 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.

  2. resolved May 14, 2025, 06:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 4, 2024

Vault OAuth flow degredation

Detected by Pingoru
Oct 04, 2024, 04:25 PM UTC
Resolved
Oct 04, 2024, 11:12 PM UTC
Duration
6h 47m
Affected: Vault API
Timeline · 2 updates
  1. investigating Oct 04, 2024, 04:25 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 04, 2024, 11:12 PM UTC

    This issue was resolved approximately 44 minutes from the time of initial report.

Read the full incident report →