Frequently Asked Questions
Find answers to common questions about our platform reliability metrics, status updates, monitoring intervals, and reporting issues.
FireAPI operates on a multi-region distributed infrastructure providing high redundancy. Our historical platform uptime is maintained above 99.98%.
Operational status indicates that all core microservices, including database components and the request routing API gateways, are running and responding within optimal latency thresholds.
A partial outage indicates that one or more specific subcomponents (e.g., developer console or search query indexers) are experiencing performance degradation or connection issues, but the core request processing gateway remains functional.
Uptime calculations and health checks are run dynamically every 60 seconds from distributed edge servers globally.
If you suspect an outage not listed on this status page, please contact our support team at support@fireapi.io or open a critical ticket through the developer dashboard console.
Yes, we perform rolling database and storage optimization updates. These are scheduled during low-traffic hours (typically 2:00 AM UTC on weekends) and are announced in advance on the Maintenance page.
You can query our machine-readable status file directly at status.json. This can be integrated directly inside your health check or notification workflows.