Changes / Secureframe / Secureframe Agent unable to connect
Secureframe: Critical incident: Secureframe Agent unable to connect
Summary
Secureframe reported a critical outage: Secureframe Agent could not connect to internal services, leaving it unable to operate and/or report. It lasted 20 h 22 min, from 2024-04-04 21:20 UTC to 2024-04-05 17:42 UTC. Secureframe implemented a fix and said it was working on an Agent update to reduce susceptibility to similar interruptions.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Secureframe Agent unable to connect
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2024-04-04 21:20 UTC
Before: not present
After: 2024-04-05 17:42 UTC
Before: not present
After: Secureframe Agent
Before: not present
After: The Secureframe Agent is not connecting to internal services at this time. This renders Secureframe Agent unable to operate and/or report. We are working on remediation strategies at this time.
Before: not present
After: A fix has been implemented and we are monitoring the results.
Before: not present
After: This incident has been resolved. We are working on updating the Secureframe Agent to be less susceptible to service interruptions of this nature.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Secureframe Agent unable to connect (this change) Secureframe reported a critical outage: Secureframe Agent could not connect to internal services, leaving it unable to operate and/or report. It lasted 20 h 22 min, from 2024-04-04 21:20 UTC to 2024-04-05 17:42 UTC. Secureframe implemented a fix and said it was working on an Agent update to reduce susceptibility to similar interruptions. | Major incident |
All Secureframe changes → · Secureframe profile · Markdown · JSON