Vendor record
OpenSSL
No current status check to show
Front door check counts and OpenSSL’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We have no front door checks against OpenSSL in the last 30 days. That does not show whether it was reachable.
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every OpenSSL product, region or your app worked.
How we count front door checksOpenSSL says
Incident posts from OpenSSL’s status page, with its titles, impact levels and times. They say what OpenSSL chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
0
incidents OpenSSL posted, last 30 days
Most recent records · all dates
No incidents recorded
OpenSSL has posted nothing we recorded. That is an empty history, not evidence of uninterrupted service.
Your code, your dependencies
See which of your code paths call OpenSSL
Connect GitHub or GitLab to find where your public or private repository uses OpenSSL. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add OpenSSL status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Does CheckUpstream monitor OpenSSL?
No. OpenSSL is in the CheckUpstream catalog so that packages resolving to it are recognised in a dependency graph, but it is not polled and no status is published for it.
Why not?
OpenSSL does not currently have supported status monitoring in CheckUpstream. A catalog entry can help identify a repository dependency; it does not establish that a status feed or independent checks are available.