Infisical Outage History

Infisical is up right now

There were 3 Infisical outages since February 12, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.infisical.com

Minor April 17, 2026

US and EU Cloud experiencing UI rendering issues

Detected by Pingoru
Apr 17, 2026, 12:35 AM UTC
Resolved
Apr 17, 2026, 12:35 AM UTC
Duration
—
Affected: PAMSecrets managementPKI
Timeline · 2 updates
  1. investigating Apr 16, 2026, 11:32 PM UTC

    Status: Investigating We're investigating reports of EU and US Cloud's UI not rendering. We'll provide an update shortly as we dig further into our metrics. The API is fully operational, this issue is purely isolated to the Web UI. Affected components PAM (Partial outage) PKI (Partial outage) PAM (Partial outage) Secrets management (Partial outage) Secrets management (Partial outage) PKI (Partial outage)

  2. resolved Apr 17, 2026, 12:35 AM UTC

    Status: Resolved This incident has been resolved. All services are operating normally. We apologize for any inconvenience caused. Affected components Secrets management (Operational) PKI (Operational) PAM (Operational) PKI (Operational) PAM (Operational) Secrets management (Operational)

Read the full incident report →

Minor February 12, 2026

Service disruptions in US Cloud

Detected by Pingoru
Feb 12, 2026, 10:47 AM UTC
Resolved
Feb 12, 2026, 10:47 AM UTC
Duration
—
Affected: PAMSecrets managementPKI
Timeline · 4 updates
  1. investigating Feb 12, 2026, 10:17 AM UTC

    Status: Investigating We're investigating reports of service disruptions in US Cloud. We'll provide an update shortly as we dig further into our metrics. Affected components Secrets management (Degraded performance) PKI (Degraded performance) PAM (Degraded performance)

  2. identified Feb 12, 2026, 10:22 AM UTC

    Status: Identified We've identified the cause to be associated with Redis failover. Our team is working on remediation effort. Affected components Secrets management (Degraded performance) PKI (Degraded performance) PAM (Degraded performance)

  3. monitoring Feb 12, 2026, 10:28 AM UTC

    Status: Monitoring We've triggered a redeployment to re-establish connections to the failed-over Redis instances. Services should be returning to normal, and we'll confirm full resolution shortly. Affected components Secrets management (Degraded performance) PKI (Degraded performance) PAM (Degraded performance)

  4. resolved Feb 12, 2026, 10:47 AM UTC

    Status: Resolved This incident has been resolved. All services are operating normally. Affected components PAM (Operational) Secrets management (Operational) PKI (Operational)

Read the full incident report →

Minor February 12, 2026

Service disruption in US Cloud

Detected by Pingoru
Feb 12, 2026, 06:12 AM UTC
Resolved
Feb 12, 2026, 06:12 AM UTC
Duration
—
Affected: PAMSecrets managementPKI
Timeline · 7 updates
  1. investigating Feb 12, 2026, 05:30 AM UTC

    Status: Investigating We're investigating reports of US Cloud service disruptions. We'll provide an update shortly as we dig further into our metrics. Affected components PAM (Degraded performance) Secrets management (Degraded performance) PKI (Degraded performance)

  2. identified Feb 12, 2026, 05:37 AM UTC

    Status: Identified We've identified the root cause as out-of-memory issues with our caching system. Our team is currently scaling the affected service to restore normal operations. Affected components Secrets management (Degraded performance) PKI (Degraded performance) PAM (Degraded performance)

  3. monitoring Feb 12, 2026, 05:48 AM UTC

    Status: Monitoring Caching service has been scaled. Services should be returning to normal. We'll confirm full resolution shortly. Affected components Secrets management (Degraded performance) PKI (Degraded performance) PAM (Degraded performance)

  4. resolved Feb 12, 2026, 05:51 AM UTC

    Status: Resolved This incident has been resolved. All services are operating normally. Affected components Secrets management (Operational) PKI (Operational) PAM (Operational)

  5. investigating Feb 12, 2026, 06:00 AM UTC

    Status: Investigating We are investigating reports of disruption Affected components Secrets management (Full outage) PKI (Full outage) PAM (Full outage)

  6. monitoring Feb 12, 2026, 06:02 AM UTC

    Status: Monitoring A fix has been deployed and we're monitoring the results. Services should be returning to normal. We'll confirm full resolution shortly. Affected components Secrets management (Operational) PKI (Operational) PAM (Operational)

  7. resolved Feb 12, 2026, 06:12 AM UTC

    Status: Resolved This incident has been resolved. All services are operating normally. We apologize for any inconvenience caused. Affected components PKI (Operational) PAM (Operational) Secrets management (Operational)

Read the full incident report →

Looking to track Infisical downtime and outages?

Pingoru polls Infisical's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Infisical reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Infisical alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Infisical for free

5 free monitors · No credit card required