Skip to main content
Infisical logo

Is Infisical Down?

No — Infisical is up

Reachable from all 8 checked regions

Average response time: 343ms

Last checked · checks run every 6 hours

Official status page: https://status.infisical.com

Infisical uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
257ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 34 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

34-day clean streak
Sep 12: 100.00% uptime, 31 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 30 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 30 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Sep 12 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra
105ms
DNS 9ms TCP 1ms TLS 10ms TTFB 94ms
gru
459ms
DNS 138ms TCP 3ms TLS 18ms TTFB 439ms
iad
137ms
DNS 32ms TCP 2ms TLS 9ms TTFB 129ms
jnb
724ms
DNS 171ms TCP 1ms TLS 8ms TTFB 715ms
lax
122ms
DNS 22ms TCP 2ms TLS 10ms TTFB 111ms
lhr
299ms
DNS 108ms TCP 2ms TLS 9ms TTFB 287ms
nrt
458ms
DNS 109ms TCP 1ms TLS 8ms TTFB 452ms
ord
443ms
DNS 67ms TCP 15ms TLS 27ms TTFB 388ms

What Infisical does

Infisical is a secrets management platform where teams store API keys, database credentials and configuration, then pull them into applications and CI pipelines at runtime through its SDKs, CLI and Kubernetes operator. It is offered as a shared cloud in separate US and EU deployments, as a dedicated cloud, and as open-source software teams run themselves.

What an outage looks like

Deployments and CI jobs fail at the point of fetching secrets, usually with a timeout or an authentication error from the Infisical client rather than anything descriptive. Already-running services keep working on the secrets they hold in memory, so nothing breaks until something restarts, which makes the blast radius grow with every deploy and every pod reschedule.

What to do about it

Read status.infisical.com and find your deployment, because it reports Infisical Shared Cloud (US) and Infisical Shared Cloud (EU) as separate groups of components, with Infisical Dedicated Cloud and Artifacts separate again. An incident on the US region says nothing about the EU one. Pause non-urgent deploys during an incident so running workloads keep the secrets they already have, and avoid restarting healthy services until the region recovers.

Is it down for everyone, or just you?

If this page says Infisical is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

HashiCorp
HashiCorp
1Password
1Password
LastPass
LastPass
AWS
AWS

Infisical outage FAQ

My running services are fine but deploys fail. Is Infisical down?
That is the usual shape. Applications fetch secrets at startup and hold them in memory, so an incident does not disturb anything already running while every new deployment, restart or scaled-up pod fails at the fetch. The impact is invisible until something restarts, then arrives suddenly. Check the components for your region on status.infisical.com before debugging your pipeline.
Does an incident on Infisical's US cloud affect the EU cloud?
Not necessarily. Infisical publishes Infisical Shared Cloud (US) and Infisical Shared Cloud (EU) as separate groups, each with its own components, and Infisical Dedicated Cloud separately again. Find the group matching the deployment your organisation is on. A global all-clear headline is less useful here than the specific group, and colleagues on a different deployment prove nothing either way.
I self-host Infisical. Does the status page apply?
No. status.infisical.com covers the shared and dedicated clouds Infisical operates. A self-hosted instance runs on your own infrastructure with its own database and network, so an incident there is unrelated and an all-clear does not clear your deployment. Check your own instance, its database and the network path from your workloads first.
Should I hard-code secrets to get through an Infisical outage?
Avoid it. Secrets pasted into environment files or CI variables under time pressure tend to outlive the incident, spread into logs and version control, and are exactly what the platform exists to prevent. If a deploy genuinely cannot wait, use a short-lived local copy you have a specific plan to remove, and rotate anything that was exposed once the incident is over.
Is Infisical down or is my machine identity misconfigured?
Compare scope. An authentication fault affects one identity, project or environment and usually follows a token expiry or a permissions change, while an incident affects every fetch against that deployment at once. status.infisical.com names the affected component. If the page is all-clear and only one pipeline fails, check that identity's credentials and its access to the project first.

How we measure this

  • We request Infisical's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Infisical publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Infisical goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required