Skip to content
Status

System status

What is up, what is not, and what we did about the last thing that broke. Updated as incidents happen, not after the post-mortem.

All core services operational

One connector is running slow — detail below.

Web application
99.99% 90d Operational
API
99.98% 90d Operational
Background jobs & email queue
99.95% 90d Operational
File storage & documents
100% 90d Operational
Payment gateway connectors
99.71% 90d Degraded
Scheduled reports
99.97% 90d Operational

Recent incidents

MONITORING 2 August 2026, 14:10 WAT

Slow settlement callbacks from one payment provider

Callbacks are arriving 4–9 minutes late, so receipts post later than usual. Payments are not lost and reconciliation is unaffected. We are queuing and retrying while the provider investigates.

RESOLVED 21 July 2026, 09:32 WAT · 26 minutes

Email queue backlog

Primary SMTP authentication failed after a credential rotation. The fallback route took over automatically, so no message was lost, but invitations and reminders were delayed. Credentials rotated and an alert now fires on the first primary failure rather than the hundredth.

RESOLVED 4 July 2026, 22:00 WAT · scheduled

Database maintenance window

Planned index rebuild on the ledger tables. Read-only for 40 minutes as announced.

Want incidents by email? Subscribe from the footer, or write to support@primeerp.com.