This page states the availability commitment Eslam Osama Mohamed, trading as INFRO, makes for the INFRO gateway, how availability is measured, and what the commitment does not include. It forms part of the Terms of service for the organizations it covers.
The commitment
The INFRO gateway will be available at least 99.9% of the measured minutes in each calendar month, in UTC. In a 30-day month that allows up to 43 min of downtime.
The gateway is the API at api.infro.io that receives your applications' requests and routes them to the AI provider accounts you connected. The consoles, INFRO Studio, the MCP server, this website and the documentation are operated with the same care and are not part of the measured figure.
Who it covers
The commitment covers organizations on the Business plan and organizations with an enterprise agreement, for as long as the subscription is active. Trials of the Business plan are covered in the same way. Organizations on the Developer, Startup and Team plans use the same gateway and can read the same measured figures, without a commitment.
A target, without a financial remedy on a published plan
On a published plan the commitment is a target. If a month falls below 99.9%, the month is shown as missed on the status page with the downtime that caused it. It does not entitle you to a refund, a discount or any other payment, and it does not extend your subscription.
Where an enterprise agreement states remedies for availability, that agreement governs and takes precedence over this page. Nothing here limits the refund and cancellation policy or rights you hold under mandatory law.
How availability is measured
Once a minute the gateway's scheduler records a check: that it ran, that it reached the database every request depends on, and that the gateway's own readiness check answered. A minute counts as downtime when:
- its check failed;
- it falls in a run of more than 2 consecutive minutes in which no check was recorded at all, which is what an outage of the gateway or its database looks like from the inside; or
- it falls inside an outage our staff recorded. This is how a failure the checks cannot see, such as requests failing while the scheduler is healthy, reaches the figure.
A gap of one or two minutes without a check is a deploy or a delayed tick of the scheduler and is not counted. Uptime for a month is the measured minutes that were not downtime, divided by the measured minutes. Percentages are rounded down, never up.
Every figure is published on the status page with the period it was measured over and the time it was computed. Minutes before the first recorded check are not measured, and no figure is shown for them.
What the measurement cannot see
The checks run inside INFRO's own infrastructure. They are not an independent, third-party measurement, and they do not observe the network path between your application and the gateway. The status page also runs a live check from your own browser so you can test that path yourself. If you believe the gateway was unavailable to you during a period the status page shows as available, write to support@infro.io with the time and a request id; where we confirm it, we record the outage and it counts.
What is not counted as downtime
- Your AI providers. A request that fails, slows or is refused at a provider you connected is not gateway downtime, whether or not a route fails over to another of your connections. The request log names the provider and the attempt that failed.
- Announced maintenance. A maintenance window published on the status page at least 48 hours before it begins is excluded from the month. A window announced with less notice is shown, and any downtime inside it counts.
- Requests the gateway refuses by design. A budget or spend cap you set, a model your policy does not allow, a rate limit, a disabled or revoked key, a guardrail, an invalid request, or an organization that is suspended or has no active subscription.
- Problems outside the gateway. Your own network, DNS, code and configuration, and internet routing between you and the gateway.
- The sandbox environment and features marked as preview.
Changes to this commitment
We may change this commitment. A change that lowers the target or narrows who is covered is announced to the owners of covered organizations before it takes effect and applies from the start of the following calendar month at the earliest.
Contact
Questions about this commitment: support@infro.io. To discuss availability terms with remedies, see enterprise agreements.