Freyt365 Status — Incident in progress

Major outage

Incident INC-2026-—

Elevated error rates on edge compute (upstream provider incident)

We’re investigating an ongoing incident with our hosting provider that is causing 503 errors and intermittent timeouts across the Freyt365 platform. User-facing pages, the wallet, and fuel-order flows are currently unavailable. Administrative and API surfaces may remain partially reachable. We’ll post updates here as we have them.

Incident started—

Last update—

Environmentproduction

Edge regionsaf-south-1 · eu-west-1 · us-east-1

Next update in≤ 15 min

Affected components

Web · freyt365.com

Consumer pages, dashboards, marketing

Major outage

API · /api/*

Wallet, fuel orders, transactions, webhooks

Degraded

Edge network

Serverless functions, SSR, routing

Major outage

Database · primary

Postgres / Supabase

Operational

WhatsApp messaging · Kapso / Meta

Notifications, OTP, flows

Partial failure

CDN · static assets

Fonts, images, bundled JS/CSS

Operational

Updates

—

Investigating Elevated 5xx responses from edge network

Our monitoring detected a spike in HTTP 503 and ECONNRESET errors originating from our hosting provider’s edge compute layer. Initial triage suggests the incident is upstream and affects multiple regions. No data loss has been observed.

—

Investigating Cascading failures reported on wallet & fuel-order endpoints

Users are seeing blank pages or generic error messages on consumer surfaces. Admin console and database remain reachable. We’ve opened a high-priority ticket with the provider and are coordinating on mitigation.

—

Identified Upstream provider acknowledged the incident

The provider has confirmed an ongoing issue on their side affecting serverless function execution in the regions we deploy to. ETA to mitigation is not yet available. We’re holding automated user-facing traffic on a maintenance page to prevent cascading failures on downstream partners (fuel providers, mobile-money rails).

Recent log tail — edge router