/ Status

All systems operational.

Operational

All GIWAHS platform components are operational. This page is the public record of component status, incident history, and scheduled maintenance — automated uptime metrics publish here as our public monitoring programme rolls out.

Page generated: 2026-09-03 · Updated with every platform release

/ 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.

Current status

All systems operational

8 of 8 components

Customer-impacting incidents

Since public launch

Public uptime reporting

Launching

30 / 90-day and 12-month windows

As public monitoring launches, 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 our Security & Incident Response Policy), 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.

Email status@giwahs.com to be added to the announce list.

Email status@giwahs.com

/ See also