/ Status

All systems operational.

Operational

This is a public review-only status page. Component status, uptime metrics, and incident history will be populated by a monitoring source once founder approval is granted to wire the integration. The structures below are the planned reporting shape.

Page generated: 2026-07-06 · Source: review-only reference structure

/ 01 — Component status

Live component breakdown.

Marketing site

Public marketing surfaces (giwahs.com / *.giwahs.com)

Operational

Buyer & supplier app

Authenticated buyer and supplier experiences

Operational

Backend API

FastAPI services behind /api/*

Operational

Database (Supabase)

Primary Postgres + RLS policies + audit log

Operational

Authentication

Supabase Auth (sign-in, sessions, password reset)

Operational

Payments (Stripe)

Subscription processing, Customer Portal, Stripe Tax

Operational

Email dispatch (Resend)

Transactional email + lifecycle notifications

Operational

Edge & CDN (Cloudflare)

CDN, WAF, DDoS mitigation, bot management

Operational

Membership cron

Renewal + verification reminder dispatcher (post-activation)

Planned

Note: Membership cron is marked Planned until activation is approved.

/ 02 — Uptime reporting (planned)

Reporting structure ready, values pending.

30-day uptime

—

Will publish once monitoring source is wired

90-day uptime

—

Reporting structure prepared (see below)

12-month uptime

—

Reporting structure prepared

Once monitoring is wired, this section will publish: (a) rolling 30/90/365-day uptime, calculated as customer-impacting up-minutes / total in-window minutes; (b) per-component availability for each of the components listed in section 01; (c) a 30-day sparkline strip for each component.

/ 03 — Incident history

12-month rolling window.

No customer-impacting incidents recorded.

When an incident occurs, a card will appear here with: ID, started/resolved timestamps, severity (SEV-1 to SEV-4 per Doc 30 §12), components affected, summary, and timeline updates.

Severity model: SEV-1 (confirmed breach / prod down) → SEV-4 (informational) — see Trust · Security.

/ 04 — Scheduled maintenance

Notices, with advance warning.

No scheduled maintenance.

Customer-impacting maintenance windows will be posted here at least 7 days in advance and will repeat 24 hours before the window opens.

/ 05 — Subscribe to status updates

Get notified of incidents and maintenance.

Subscription endpoints will activate once monitoring is wired. Until then, email status@giwahs.com to be added to the announce list.

Email status@giwahs.com

/ See also