Uptime — Flowie Platform Status
Status monitoring is currently being instrumented. Live uptime metrics and incident history will appear here once monitor wiring is complete (expected Q3 2026). In the meantime, contact support@flowie.fr to report a service issue or confirm platform availability.
SLA targets and credit terms are documented separately at View SLA Details.
Real-time
Current status
Monitor wiring is in progress. The status panel will appear here once BetterUptime synthetic monitors are connected to all production endpoints. Estimated: Q3 2026.
Monitor wiring in progress
BetterUptime synthetic monitors are being connected to all production endpoints. Live status will appear here once wiring is complete (expected Q3 2026). For urgent service questions, email support@flowie.fr.
30-day · 90-day · YTD
Uptime metrics
Live metrics coming online Q3 2026. SLA targets are documented separately.
| Service | 30-day uptime | 90-day uptime | YTD uptime | SLA target |
|---|---|---|---|---|
| API gateway | — | — | — | 99.9% (Standard) / 99.95% BH, 99.9% OBH (Enterprise) |
| Web application | — | — | — | 99.9% (Standard) / 99.95% BH, 99.9% OBH (Enterprise) |
| E-invoicing endpoints | — | — | — | 99.9% (Standard) / 99.95% BH, 99.9% OBH (Enterprise) |
| Integrations layer | — | — | — | 99.9% (Standard) / 99.95% BH, 99.9% OBH (Enterprise) |
Methodology
How we measure
Flowie uses BetterUptime synthetic transaction monitoring. Monitors run every 5 minutes from 3 geographically distributed probe locations. Each probe executes an end-to-end transaction against the monitored endpoint — not a simple ping.
What counts as downtime: A service is considered down when it is unavailable or returns errors to more than 50% of users for more than 5 consecutive minutes as measured across all three probe locations.
What is excluded from downtime calculations:
- Scheduled maintenance windows (≤4 hours cumulative per quarter, announced ≥7 days in advance, preferably Sundays 02:00–04:00 CET)
- Force majeure events outside Flowie's reasonable control
- Degradation caused by customer-side configuration, customer-controlled infrastructure, or third-party services not under Flowie's operational control
Past 90 days
Incident history
The incident log will publish once monitor backfill completes.
No resolved incidents to show yet — the incident log will publish here once BetterUptime monitor backfill completes.
Severity classifications: S1 critical (customer notification + war-room); S2 high (accelerated response); S3 medium (tracked); S4 low (normal change management). GDPR Article 33 personal data breach notifications operate on a separate 72-hour regulatory timeline, independent of operational incident severity.
Email · Slack
Subscribe to status updates
Get notified before and during any service event.
If the widget below does not render, subscribe directly at flowie.betteruptime.com.
What you receive:
- Maintenance notifications — minimum 7 days advance notice before any scheduled window
- Incident notifications — within 5 minutes of a monitor triggering, for S1 and S2 events
- Resolution notifications — when a service is confirmed restored
Notification channels: email and Slack (via BetterUptime).
Read this together with /sla
How this relates to our SLA
The uptime figures and incident log on this page are published for operational transparency. They include all events — including scheduled maintenance windows — so that operations and IT teams have the full picture.
Scheduled maintenance windows are excluded from SLA calculations even though they appear here for transparency. SLA uptime calculations use net available time only.
For details on uptime commitments by tier, credit eligibility, credit request process, and force majeure exclusions, see the SLA page.
Buyers ask us this
Frequently asked questions
What operations and IT leaders ask before signing a contract or running a procurement-side review.
Is Flowie down right now?
What counts as downtime?
How far back is your incident history?
Can I subscribe to status updates?
How do you measure uptime?
Next steps
Read this with the SLA, then check our broader security posture.
Uptime is one half of the picture. SLA terms set the contractual commitments; the security page lays out controls, certifications, and breach procedures.