Is Secureframe Down?
- Secureframe's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 625 ms
Right now
The verdict is the worse of these two. How we decide
Secureframe's status page
status.secureframe.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Marketing Website | Operational |
| Web Application | Operational |
| API | Operational |
| Help Desk | Operational |
| Secureframe Agent | Operational |
| Trust | Operational |
| Security Questionnaires | Operational |
FlareWarden checks
secureframe.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 625 ms
- Checked
By region
- Amsterdam reachable, 497 ms
- Chicago reachable, 332 ms
- San Jose reachable, 332 ms
- Singapore reachable, 936 ms
- Stockholm reachable, 532 ms
- Sydney reachable, 1652 ms
- Tokyo reachable, 481 ms
- Toronto reachable, 239 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 40 ms | 5 ms | 18 ms | 404 ms |
| Chicago | 132 ms | 1 ms | 26 ms | 308 ms |
| San Jose | 19 ms | 2 ms | 23 ms | 257 ms |
| Singapore | 189 ms | 3 ms | 6 ms | 719 ms |
| Stockholm | 45 ms | 1 ms | 10 ms | 308 ms |
| Sydney | 7 ms | 1 ms | 9 ms | 1232 ms |
| Tokyo | 73 ms | 1 ms | 10 ms | 473 ms |
| Toronto | 34 ms | 18 ms | 22 ms | 187 ms |
History
Incidents Secureframe reported
Since Oct 22, 15 days · from status.secureframe.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Secureframe website availability
Measured by FlareWarden · secureframe.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 551ms
Last 30 days
65-day clean streakMeasured by FlareWarden's own checks of secureframe.com from multiple regions every 6 hours. Secureframe's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 65 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Secureframe does
Secureframe automates security compliance for frameworks such as SOC 2, ISO 27001 and HIPAA. It connects to cloud accounts and internal systems, collects evidence continuously, tracks controls and policies, and runs an agent on employee devices to check disk encryption and screen locks. Companies preparing for or maintaining an audit run their evidence collection through it.
What an outage looks like
The web application fails to load or controls show stale evidence, and device checks stop reporting. Secureframe reports the Secureframe Agent as its own component, so evidence collection from employee laptops can stop while the console looks normal. Trust and Security Questionnaires are separate again, so a customer-facing trust page can fail while internal work continues.
What to do about it
Read status.secureframe.com and match the failing component to what you need. If the Secureframe Agent row is affected, treat the gap as missing evidence rather than a failed control and confirm coverage once it recovers. If Trust or Security Questionnaires is affected, tell your sales team, because a prospect reviewing your trust page will see the failure directly.
Is it down for everyone, or just you?
If this page says Secureframe 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.
Related services
Secureframe outage FAQ
My Secureframe console works but device checks stopped. Is that an outage?
Does a Secureframe outage affect my audit?
Customers cannot open our trust page. Is that us or Secureframe?
Is Secureframe down for everyone or just my account?
How we measure this
- We request Secureframe'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
403or429means 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 Secureframe 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 Secureframe 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 Secureframe goes down
We check Secureframe 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