Reliability

IronCore's APIs are built on Google Kubernetes Engine (GKE) and are designed to take advantage of self healing, multi-region, and multi-zone capabilities. We strive to provide low latency service to customers, worldwide. If one zone is experiencing an issue, we will begin directing traffic to another until the issue is resolved. If one pod is unhealthy, requests will automatically be directed to a healthy one while the ailing pod recovers or is automatically replaced.

Each backend service can expand, dynamically, to meet increased demand. No matter the time of day, load, or geographic location, we provide dependable, predictable performance.

Every piece of data you entrust to us is automatically backed up and stored in at least one additional zone. Along with our high availability architecture, this keeps your data available when you need it.

We know that the unexpected happens, and we have processes in place to enable our engineering team to address issues from first alert to final resolution. While we can't imagine every situation, we have planned for the ones we can imagine, and promise to always communicate with you as we work toward a solution.

We believe in sunshine and transparency and that means with uptime, too. We publish our uptime and monitoring on a public website allowing anyone to follow and track issues. Watching the associated Github repository will give email alerts. Additionally, this is where we post planned downtime and maintenance notices. Such notices may also be posted on our community discussions board and in the "Announcements" channel on our Discord server (invite link).

We schedule planned downtime, to the extent reasonably practicable, during the weekend hours from 5:00 p.m. Mountain Time Friday to 3:00 a.m. Mountain Time Monday. Our database maintenance window is Sunday from 1:00 p.m. to 2:00 p.m., so we typically schedule other maintenance during that time. maintenance is scheduled for Sunday afternoons, Mountain Time.