Incident history

Incident history and reporting boundaries.

This page records the public incident-history boundary for Shhhs. The current live posture remains available at status.shhhs.net.

01

Current status

The current public service status is available at status.shhhs.net. That page combines live Shhhs checks with Cloudflare public status where available.

  • status.shhhs.net
  • Cloudflare status link
  • No invented uptime history

02

History boundary

Shhhs publishes incident information when there is a confirmed customer-impacting event that can be described without exposing secrets, tokens, personal data, or sensitive operational details.

  • Confirmed customer impact
  • No secret disclosure
  • Metadata-only incident notes

03

No historical SLA claim

This page does not claim a historical uptime percentage, external SLA, or certification-backed incident program. Enterprise SLA or incident terms require a reviewed commercial agreement.

  • No uptime percentage claim
  • No SLA by default
  • Enterprise review by contact

04

Reporting an issue

Use the security report page for vulnerabilities and the contact page for support, billing, privacy, legal, or Enterprise escalation. Reports must use test data and avoid secrets, tokens, OTPs, recovery codes, passphrases, and full private links.

  • Security reports
  • Support contact
  • Test data only

05

Current public record

No public customer-impacting Shhhs incident has been published for this service version. If that changes, this page should be updated with date, impact, status, resolution, and remediation notes.

  • No published incident for this version
  • Update on confirmed incident
  • No sensitive artifacts

FAQ

Does Shhhs process secrets with AI?

No. There is no AI processing on secret content.

Can Shhhs recover a secret?

No. Secret recovery would weaken the privacy model.

What can support recover?

Support can help cancel billing after billing validation, but cannot restore account access or secret content.