Snapshot 222324
Normalized text
Scripts and page chrome removed; this is what change detection compares.
HailBytes Status Operational status of HailBytes-operated infrastructure. Last reviewed 2026-05-11. What this page covers: the small footprint of HailBytes-operated infrastructure: the public container registry, the Marketplace listings, the marketing site, and the HailBytes-built Support Hub on Cloudflare. None of these are on the critical path for a running HailBytes ASM or HailBytes SAT deployment in a customer's cloud account. What this page does not cover: customer-deployed instances of HailBytes ASM or HailBytes SAT. Those run inside the customer's own AWS or Azure account (see BYOC architecture) and their operational status is visible to the customer through their own cloud-provider tooling. A HailBytes-side incident does not bring down a customer deployment. Current component status Container registry (ghcr.io/hailbytes/*) Public container registry serving release images for ASM and SAT. Operated by GitHub. Status: Operational AWS Marketplace listings ASM and SAT listings on AWS Marketplace. Operated by AWS. Status: Operational Azure Marketplace listings ASM and SAT listings on Azure Marketplace. Operated by Microsoft. Status: Operational hailbytes.com (marketing site) Statically generated; deployed via Cloudflare Pages. Status: Operational Support Hub HailBytes-built application on Cloudflare Workers + Pages with KV/D1 storage. Notifies HailBytes personnel of pending support and integration tickets. Status: Operational Build & release pipeline (GitHub Actions) CI/CD for ASM and SAT release artifacts: SBOMs, SARIFs, Cosign signatures, Trust Pack archives. Status: Operational Recent incident history No HailBytes-side incidents on record for the past 90 days. This page is updated within one hour of incident declaration; the security mailing list is the primary notification channel and incident detail flows there first. Subscribe to incident notifications Enterprise customers are added to the security mailing list at contract signature. Public subscription (for security researchers, partners, or anyone watching HailBytes' operational posture) is available by emailing [email protected] with subject "Subscribe: security advisories." For HailBytes' written posture on customer continuity under HailBytes-side incidents, see BCP/DR plan and the annual tabletop exercise.