Infisical
Infisical is operational
Checked 46 s ago Operational
History
90 days agoToday
Incidents in 90 days
0
Days with an incident
0
Median duration
No data
Longest incident
No data
Components
9Secrets management Operational
90 days agoNo incidentsToday
PAM Operational
90 days agoNo incidentsToday
PKI Operational
90 days agoNo incidentsToday
Secrets management Operational
90 days agoNo incidentsToday
PAM Operational
90 days agoNo incidentsToday
PKI Operational
90 days agoNo incidentsToday
Infisical Dedicated Cloud Operational
90 days agoNo incidentsToday
Infisical CLI repository Operational
90 days agoNo incidentsToday
Helm repository Operational
90 days agoNo incidentsToday
No incident in the last 90 days.
Follow Infisical
Your coding agent knows when Infisical is down, and tells you when a failure is theirs, not yours. You can also get Infisical incidents in a feed reader or in Slack.
Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "infisical" and tell me if Infisical has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
RSS
https://outages.cc/feed.xml?providers=infisicalSlack
/feed subscribe https://outages.cc/feed.xml?providers=infisicalGo from tracking outages to fixing production issues with Polylane.
Try Polylane