Availability & Status
Your finance system has to be there at 9pm before payroll runs and at quarter close. Fintra targets 99.9% monthly uptime, performs maintenance in published low-traffic windows, communicates incidents in plain language on the status page and by email, and backs it all with tested disaster-recovery objectives.
Uptime target
Fintra targets 99.9% availability measured monthly - roughly 43 minutes of allowable downtime per month - excluding published scheduled maintenance. Availability is measured by external synthetic checks against core user journeys (sign-in, ledger reads, report generation), not just server ping, because "up" only counts if you can actually close your books. Uptime performance is tracked as a SentriAI availability control, so misses trigger internal review automatically.
Maintenance windows
Most releases deploy with zero downtime. When disruptive maintenance is unavoidable, it is scheduled and announced, not sprung.
- Standard window: weekends, 02:00–06:00 US Eastern, chosen for minimal SMB finance activity.
- Announced at least 72 hours in advance on the status page and by email to admins.
- Scheduled maintenance is excluded from uptime measurement only when announced in advance - unannounced work counts against us.
- Emergency security patches may ship outside windows; we notify as early as the situation safely allows.
Incident communication
When something breaks, silence is the worst response. Confirmed incidents are posted to the status page with severity, customer impact in plain language, and updates on a stated cadence (at least hourly for major incidents) until resolution. Tenant admins receive email notification for incidents affecting their data or availability. After resolution, significant incidents get a public post-mortem: what happened, why, and what we changed - because the fix matters more than the apology.
Disaster recovery: RPO and RTO
Behind the uptime number are tested recovery objectives: a Recovery Point Objective (RPO) of 24 hours or better - in practice, point-in-time recovery typically limits loss to minutes - and a Recovery Time Objective (RTO) of 12 hours for full-region failure. Encrypted backups with point-in-time recovery are restored on a recurring test schedule, and each test result is captured as SentriAI evidence, so DR readiness is verified continuously rather than assumed.
Frequently asked questions
What uptime does Fintra commit to?
We target 99.9% monthly availability, measured by external synthetic checks on real user journeys, excluding pre-announced scheduled maintenance. Contractual SLAs are available for larger customers - ask at security@fintrahub.com.
How will I know about an incident?
The status page is updated with severity and plain-language impact, with updates at least hourly during major incidents; tenant admins also get email notifications for anything affecting their data or availability.
When does maintenance happen?
In published windows - weekends 02:00–06:00 US Eastern - announced at least 72 hours ahead via the status page and admin email. Most deploys are zero-downtime and need no window at all.
How much data could I lose in a disaster?
Our RPO is 24 hours or better, and point-in-time recovery typically limits actual loss to minutes. Full-region recovery targets an RTO of 12 hours, and restore procedures are tested on a recurring schedule.
Questions about status & uptime?
Our security team answers due-diligence questions directly - documentation, DPAs, and evidence available on request.
Talk to our security team