Availability target
odds-api targets 99.9% monthly availability for production API endpoints.
This is an operational target, not a credit-backed contractual SLA unless separately agreed in writing.
Availability targets, current status signals, support expectations, and maintenance policies for teams evaluating or running odds-api in production.
odds-api targets 99.9% monthly availability for production API endpoints.
This is an operational target, not a credit-backed contractual SLA unless separately agreed in writing.
The support mailbox is monitored 7 days a week. Critical production availability issues are triaged with priority.
Email support@odds-api.net when something needs investigation.
Small, low-risk fixes may be deployed at any time and are designed for zero or very low downtime.
Larger or higher-risk maintenance receives advance email notice to affected customers when practical.
Checking current status
Recent public status is fetched from the buyer-safe status API when available. Static support and policy details remain available if that check cannot complete.
The public status view is limited to customer-facing components and recent health signals.
It does not expose raw traffic volume, customer-specific data, internal service names, infrastructure details, or source-level diagnostics.
Send production support requests to support@odds-api.net.
Do not send API secrets, passwords, or private customer data in support emails.
The team investigates, mitigates, and follows up by email when customer action or updates are needed.
Small fixes, configuration changes, and low-risk releases may ship at any time. These changes are designed to avoid downtime or keep downtime very low.
For larger or higher-risk maintenance, odds-api sends advance email notice to affected customers when practical.
Emergency reliability or security fixes may be applied immediately to protect the service.
When advance notice is practical, maintenance emails include the expected timing, affected customer-facing surfaces, expected downtime or degradation, and completion confirmation where relevant.
Availability calculations exclude scheduled maintenance, customer-side integration errors, invalid API keys, rate-limit enforcement, customer network issues, third-party provider or source interruptions, abuse or misuse, and force majeure events.