AEGIBIT
All systems operational

AEGIBIT service status.

Live operational state of every AEGIBIT surface. We monitor via Vercel, Supabase, Upstash, and GitHub's own status pages every check on this page links out to the externally verifiable signal it's sourced from. No synthetic uptime histograms.

Surfaces · 2026-05-14

Current state, per surface

  • Marketing site

    www.aegibit.com

    Signal: Vercel deployment status, bom1 Mumbai edge · Vercel platform status

    Operational

  • API endpoints

    /api/*, leads, contact, telemetry, rate limiter

    Signal: Vercel Function deploy status + Upstash Redis health · Upstash status

    Operational

  • PayMint application

    paymint.aegibit.com (separate deploy, internal pilots only)

    Signal: Vercel deployment status + Supabase Singapore region · Supabase status

    Operational

  • MCP Shield repository

    github.com/AegibitSecurity/mcp-shield, public, MIT, v0.2.1

    Signal: GitHub availability · GitHub status

    Operational

Scope of this page

AEGIBIT is early enough that we don't yet operate a multi-region observability grid or publish synthetic 90-day uptime histograms. Pretending to would be the kind of credibility miss we've spent the rest of the site eliminating.

What we domonitor: Vercel deployment health, Supabase database availability, Upstash Redis rate-limiter health, and GitHub public-repo availability, each linked above to the upstream provider's own status page so you can verify independently.

When the first paid PayMint MSA with an uptime SLA attaches, or the first independent monitoring vendor enters the stack, this page upgrades to the corresponding fidelity. Until then, this is the honest scope.

Incident history

No reported customer-impacting incidents to date.

When the first customer-impacting incident occurs, it will be posted here with timestamps, scope, root cause, and remediation, the same level of detail we'd expect a vendor to publish to us. Internal performance regressions and platform-side blips that didn't reach a customer are not posted here; they live in the changelog at /changelog.

Get notified when something breaks

Email the team and ask to be added to the incident list. We use the existing AEGIBIT mailing pipeline, incident-only, no marketing on this list, no unsubscribe friction.

Subscribe to incidents