Skip to main content
StrongDM logo

Is StrongDM Down?

No — StrongDM is up
StrongDM's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 455 ms

Right now

The verdict is the worse of these two. How we decide

StrongDM's status page

status.strongdm.com · read · checked every 3 minutes

Operational

“All Systems Operational”: no open incidents and no component reported in trouble.

6 locations All operational

FlareWarden checks

app.strongdm.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
455 ms
Checked

By region

  • Ashburn reachable, 275 ms
  • Dallas reachable, 252 ms
  • Frankfurt reachable, 340 ms
  • Johannesburg reachable, 1087 ms
  • London reachable, 392 ms
  • Los Angeles reachable, 288 ms
  • Newark reachable, 381 ms
  • São Paulo reachable, 631 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn236 ms12 ms13 ms275 ms
Dallas169 ms26 ms27 ms252 ms
Frankfurt29 ms102 ms104 ms339 ms
Johannesburg348 ms245 ms246 ms1087 ms
London117 ms91 ms91 ms391 ms
Los Angeles125 ms53 ms54 ms288 ms
Newark319 ms19 ms20 ms381 ms
São Paulo222 ms134 ms136 ms631 ms
We check that app.strongdm.com loads, not every feature behind it. Test it yourself

History

Incidents StrongDM reported

Since Nov 4, 2 days · from status.strongdm.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

StrongDM website availability

Measured by FlareWarden · app.strongdm.com

Last 7 days
—
Last 30 days
—
Last 90 days
—
Avg response, 30 days
—

Last 30 days

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

Measured by FlareWarden's own checks of app.strongdm.com from multiple regions every 6 hours. StrongDM's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What StrongDM does

StrongDM is an access platform: people connect to resources through StrongDM relays and nodes, and administrators manage access, policies and query logs in the Admin UI. strongdm.com now redirects to Delinea. Its status page lists the Admin UI and API for the US, UK and EU control planes; the US control plane is app.strongdm.com.

What an outage looks like

The Admin UI loads slowly or not at all, and API requests time out, usually on one control plane: on February 17, 2026 the US control plane was slow for about eight hours, and on October 21, 2025 the Admin UI did not load for about 30 minutes. Some incidents break connections to resources instead, as on October 2, 2025, or connections to AWS Secret Stores, as in January 2026.

What to do about it

Check status.strongdm.com and find your control plane: the US, UK and EU control planes each have their own Admin UI and API rows. StrongDM posts postmortems for larger incidents, so read them for whether an action is needed on your side. If you sign in through OneLogin, check its status too. Problems reaching the US control plane go to the support team at help.strongdm.com.

Is it down for everyone, or just you?

If this page says StrongDM 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

StrongDM outage FAQ

Can engineers still connect when StrongDM's Admin UI is down?
It depends on what the incident names. The October 21, 2025 Admin UI outage stopped the console loading for about 30 minutes, and the February 2026 US control plane slowdown delayed Admin UI and API requests. The October 2, 2025 incident was the kind that blocks people: a change to token validation made connections to resources fail for about an hour before it was rolled back.
Why did StrongDM connections to AWS Secret Stores fail in January 2026?
A relay change from January 14, 2026 was missing container credential support after a move to the Go AWS SDK v2, according to StrongDM's postmortem. In EKS environments relays could obtain the wrong IAM role, which broke connections to AWS Secret Stores for some customers; StrongDM rolled the change back after the first tickets on January 28.
Does a OneLogin problem stop StrongDM sign-in?
It has. On June 16, 2025 changes on OneLogin's side broke SAML and OIDC logins to app.strongdm.com and the StrongDM GUI client. StrongDM's workaround for SAML was to remove the trailing slash from the login URL in the StrongDM application settings in OneLogin; OneLogin reverted its OIDC change, so OIDC needed nothing.
Is StrongDM part of Delinea now?
strongdm.com now redirects to delinea.com, where the page is titled Delinea + StrongDM. StrongDM's control planes and status page still run under its own name: app.strongdm.com is still the US control plane, and status.strongdm.com still reports the Admin UI and API for the US, UK and EU control planes. This page checks app.strongdm.com, not Delinea's site.

How we measure this

  • We request StrongDM's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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 StrongDM publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of StrongDM itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when StrongDM goes down

We check StrongDM every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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