Status

status.ministrium.com shows in real time the state of every platform component, ongoing incidents, and the last 90 days of history.

Monitored components


🟢 REST API                    Operational
🟢 Web app (dashboard)         Operational
🟢 Mobile app (iOS/Android)    Operational
🟢 Donations (Stripe webhook)  Operational
🟢 Transactional email         Operational
🟢 SMS / WhatsApp              Operational
🟢 Push notifications          Operational
🟢 Reports and analytics       Operational
🟢 QuickBooks sync             Operational
🟢 Search                      Operational
🟢 Audit log                   Operational

Each component can be:

🟢 Operational — all fine.
🟡 Degraded — works but slower or with intermittent errors.
🟠 Partially down — some requests fail.
🔴 Down — feature unavailable.
🔵 Maintenance — scheduled window in progress.

Probes

We measure every 60 seconds from:

4 AWS regions (us-east-1, us-west-2, eu-west-1, sa-east-1)
3 different ISPs in each region
Datadog and Pingdom synthetic probes

If 2+ regions detect simultaneous failure, an automatic incident is declared.

Subscriptions

Get status alerts:

Email — org_admin is auto-subscribed at signup.
SMS — opt-in at status.ministrium.com.
Slack — webhook to your channel.
RSS/Atom — status.ministrium.com/feed.
API — GET status.ministrium.com/api/v1/components (no auth).

Customize which components matter: if you don’t use WhatsApp, we don’t notify on its downtime.

Notice types

Type	When
Investigating	We detected something, don’t yet know what
Identified	We understand the cause
Monitoring	We applied a fix, watching
Resolved	We confirm restoration
Post-mortem	Analysis published (Sev1/2 mandatory)

Each change triggers a new notification.

Post-mortems

For Sev1 and Sev2 incidents we publish a public post-mortem within 7 days:

Minute-by-minute timeline.
Root cause.
Why we didn’t detect earlier.
Corrective actions (process or code changes).
How to prevent recurrence.

No blame on individuals. Focus on the system. Industry-standard SRE “blameless post-mortem” style.

Public example: status.ministrium.com/incidents/2025-11-12-stripe-webhook-delay.

Scheduled maintenance

Calendar at status.ministrium.com/maintenance. Default:

Weekly window: Sunday 03:00-04:00 UTC for minor patches.
Monthly window: first Sunday of the month 03:00-05:00 UTC for upgrades.
Major changes: Sunday 03:00-08:00 UTC with 30 days’ notice.

If your church holds service at that exact time, open a ticket and we’ll shift the window.

History

status.ministrium.com/history shows incidents of the last 90 days. Filters by component and severity.

12-month metrics (auto-calculated):


REST API:           99.97%   (vs SLA 99.9%)
Web app:            99.95%
Donations:          99.99%
Email:              99.92%   (subprocessor SendGrid down 2 h in March)

Recent incidents example


2026-04-15  Sev2  20 min   API latency > 2s — DB saturation.    Resolved.
2026-03-22  Sev3  45 min   Slow reports.                         Resolved.
2026-03-08  Sev1  12 min   Donations rejecting — bad deploy.     Rolled back.

Status for your communications

When we declare a Sev1/2 affecting the service flow, we recommend:

Check status.ministrium.com.
Notify your team via the staff WhatsApp.
If the check-in kiosk fails, paper and pen + manual entry on recovery.

We have documented contingency plans for every critical feature.

Status as cultural contract

The status page is public and login-free, even if our main panel is down. It’s our transparency promise: if something breaks, you’ll see it there before we confirm.


https://status.ministrium.com/feed.atom
https://status.ministrium.com/feed.rss

Works with Slack (RSS app), Microsoft Teams, IFTTT, Zapier.