public system status
Folio platform health.
Live status for every part of the platform: the app, the database, AI drafting, media storage, and transactional email are probed in real time, with response times refreshed every few seconds. Launch-critical routes and jobs are covered by scheduled monitors below.
All systems operational
Live · updated just now · refreshes every 20s
- Operational
- 3/3
- DB latency
- 3 ms
- Active incidents
- 0
Response time
Live database probe, sampled this session
3 ms
Dependency latency
Uptime and incidents
Computed from published incident records. Uptime excludes planned maintenance.
- Uptime
- 100%
- Incidents
- 0
- Total downtime
- 0m
- Mean time to resolve
- --
Incidents by month
Last 12 months
Live services
Probed in real time from inside the platform.
Platform
Application
Serving requests
OperationalDatabase
Responding normally
3 msOperational
AI and content
AI drafting
Not configured in this environment
Not monitored
Storage and delivery
Media storage
Not configured in this environment
Not monitoredTransactional email
Configured and available
Operational
Monitored surfaces
Launch-critical routes and jobs covered by scheduled monitors and release gates.
- 60 seconds
Application liveness
Portfolios, auth screens, admin routes, and public APIs can receive traffic.
- 2 minutes
Dependency health
Generation, uploads, email, and publishing stay observable before users notice drift.
- 2 minutes
Public portfolios
Visitor-facing home, about, case study, and contact pages continue loading.
- 2 minutes
Authentication
Users can create accounts, sign in, recover access, and manage security settings.
- 5 minutes
Tenant admin
Owners and editors can manage content after authentication.
- 5 minutes
Custom domains
Connected domains resolve only after ownership, routing, and TLS checks pass.
- 10 minutes
Media processing jobs
Images, audio, video, and document thumbnails complete processing or retry safely.
- 2 minutes plus daily/weekly audit jobs
Security alerting
Critical admin activity, audit integrity, and offsite evidence remain monitored.
- 5 minutes
Error tracking
Unexpected errors are captured for triage without exposing the error console publicly.
- Polled every 20 seconds by the page
Status page
Users can see real-time component status, response times, and incident phases.
Incident history
No incidents reported. Every published incident and its resolution will appear here.
How we handle incidents
When an incident is opened it moves through these phases, and every update is posted to this page in real time.
- 01
Investigating
within 5 minutes for SEV-1
We are investigating an issue affecting wrxstack. We will share the next update as soon as the affected component is confirmed.
- 02
Identified
within 15 minutes for SEV-1
We have identified the affected component and are applying a fix or rollback. The next update will include verification status.
- 03
Monitoring
after mitigation is deployed
A mitigation is in place and we are monitoring recovery before marking the incident resolved.
- 04
Resolved
after verification passes
The issue is resolved. We will publish follow-up notes if customer action is required.