Is Obsidian Security Down?

SaaSLive status, outages, and incident history

No. Obsidian Security is up right now.

Every monitored Obsidian Security system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Obsidian Security breaks

Obsidian Security is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Obsidian Security status page

How we know: the official Obsidian Security status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report 9 Nov 2026 · 21:55 UTC

Obsidian Security Status Summary

As of 21:55 UTC on 9 November 2026, Obsidian Security is operational. PulsAPI checked Obsidian Security's official status page and found 13 of 13 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Obsidian Security, counting degraded performance as up. The latest incident, "Security Advisory: Obsidian response to GitBook Security Incident", was on Nov 3, 2026 and lasted 0 min.

Cite as: PulsAPI, “Obsidian Security status”, checked 9 November 2026, 21:55 UTC. https://www.pulsapi.com/services/obsidian-security

Obsidian Security Component Status

The main Obsidian Security systems on this page. All 13 are operational right now.

13operational

Extend

Operational

Integration Management

Operational

Notification

Operational

10 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Platform Services » Action Policies, Platform Services » Admin Authentication & SSO, Platform Services » Admin Portal and UI, Platform Services » API, Platform Services » Connections, Platform Services » Reporting, Platform Services » Workflow Integrations, Posture Management, Security Advisory, Threat Management.

See all of them free

Component statuses may change independently during partial outages.

Recent Obsidian Security Outages & Incidents

Incident history from the official Obsidian Security status page, including resolution updates.

Security Advisory: Obsidian response to GitBook Security IncidentResolved Nov 3, 2026 · 0 minResolved

Security Advisory: GitBook Security Incident Published: Nov 3, 2026 Summary Obsidian Security has assessed the security incident disclosed by GitBook on November 3, 2026, in which an attacker gained unauthorized access to some of GitBook’s infrastructure credentials. Obsidian uses GitBook to host the Obsidian Help Center documentation. GitBook has reported no evidence that documentation content was modified. Our response As response, we have rotated all GitBook access tokens and related credentials across our environments and confirmed documentation access is working as expected. The Obsidian platform, its supporting infrastructure, and customer data are not hosted on GitBook. Customer Impact We have observed no customer impact to date. No customer action is required. Customers accessing the Obsidian Help Center through the Documentation link in the Obsidian UI should re-authenticate automatically. We will update this advisory if our assessment changes. Questions For questions or any issues with accessing our product documentation, please contact your Obsidian account team or support via support@obsidiansecurity.com or the Admin Portal.

Security Advisory: Node2Shell Vulnerability (CVE-2026-111497)Started Oct 27, 2026Investigating

Security Advisory: Node2Shell Vulnerability (CVE-2026-111497) Published: Oct 27, 2026 Summary Obsidian Security has assessed the recently disclosed vulnerability known as Node2Shell (CVE-2026-111497), also referred to as HTTP2Shell. Our response We identified a limited number of affected services and are actively patching and redeploying them. As an immediate mitigation, we implemented Brotli content-encoding blocking at our production API gateways (completed Oct 26, 2026), protecting against Node2Shell and related HTTP2Shell variants. Customer Impact We have observed no customer impact to date. We will update this advisory once the patching is completed on our side. Questions For questions, please contact your Obsidian account team or support via support@obsidiansecurity.com or the Admin Portal.

Security Advisory: PHP2Shell Vulnerabilities (CVE-2026-109618, CVE-2026-109619)Resolved Oct 22, 2026 · 0 minResolved

Security Advisory: PHP2Shell Vulnerabilities (CVE-2026-109618, CVE-2026-109619) Published: Oct 22, 2026 Summary Obsidian Security has assessed the recently disclosed PHP vulnerabilities known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Our response The Obsidian platform, including its supporting infrastructure and web-based management interfaces, does not use PHP or any of the affected components. These vulnerabilities do not impact the Obsidian service, and no action is required from customers with respect to Obsidian. Our team continues to monitor for related risk from third-party applications and integrations that may use PHP. We recommend customers apply patches and follow remediation guidance from any affected vendors in their environment. Questions For questions, please contact your Obsidian account team or support via support@obsidiansecurity.com or the Admin Portal.

Obsidian Security Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Obsidian Security incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed

Aug 11100.00% average · 2 days with incidentsNov 9

Going further back: Obsidian Security uptime by month and every recorded Obsidian Security outage.

Live Obsidian Security Outage Reports

Problems reported by engineers using Obsidian Security. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total

24h agoNothing reportednow

No Obsidian Security problems reported yet.

Something wrong with Obsidian Security on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Obsidian Security

Is Obsidian Security down? Obsidian Security reports live availability for 14 components at status.obsidiansecurity.com, among them Platform Services, Admin Portal and UI and Posture Management. Track Obsidian Security outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Obsidian Security uptime at 100.00%. Response times, incident history, and SLA tracking for Obsidian Security are available on the PulsAPI dashboard.

Obsidian Security Status FAQ

Is Obsidian Security down right now?

The verdict at the top of this page comes from the latest poll of the official Obsidian Security status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Obsidian Security is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Obsidian Security recovers.

How do I check Obsidian Security uptime history?

PulsAPI tracks Obsidian Security uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Obsidian Security changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Obsidian Security outages?

PulsAPI reads the official Obsidian Security status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Obsidian Security components?

Yes. PulsAPI monitors 13 individual Obsidian Security components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Obsidian Security goes down?

Yes. Create a free account and subscribe to Obsidian Security: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Obsidian Security to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Obsidian Security problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Obsidian Security?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Obsidian Security plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Obsidian Security with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services