Skip to main content
Servix Iran market data API

Service status

Current component signals and independent monitoring.

Monitored components are operational.

Status evaluated:

Measured components

Authenticated API

Automated authenticated request (same host)

Operational

Application process

Current process response

Operational

Market-data freshness

Latest recorded market fetch

Operational

These same-host signals do not establish host or network uptime, complete dependency health, or an SLA. Independent API evidence appears separately in Checkly below.

Independent monitor by Checkly

Independent authenticated API monitoring

API status in Checkly monitoringOperational

Checkly independently checks the public HTTPS health endpoint with a dedicated API key. It verifies reachability and authentication, not market-data delivery or an SLA.

Recorded-check success rate

99.94%

Data recorded on 7 of 7 days

1,770 of 1,771 recorded checks succeeded

Selected period

– (UTC)

Daily Checkly history

Today
  • All recorded checks succeeded
  • No successful checks
  • Partial success or retries
  • No recorded checks

Latest external check (UTC)

Last monitoring data refresh (UTC)

Last history synchronization (UTC)

Servix refreshes monitoring data every 5 minutes

Checkly checks the API every 5 minutes

View Checkly status page (opens in a new tab)

The source-backed record above combines process reachability, the latest market fetch, an automated same-host authenticated request, optional current Operations overrides, and published incidents. The authenticated probe traverses public HTTPS but shares the application host failure domain. Unknown means required automated evidence is unavailable; no signal is an uptime percentage or SLA result.

Status owner: Servix Operations. Automated evidence updates component state. An authorized operator can publish only a current degradation, maintenance, or outage override; a stale override has no effect on current automated evidence.

What this page covers

  • customer access to the website, account, checkout, support, and authenticated API;
  • verified degradation or outage affecting the API or configured data providers;
  • planned maintenance that is expected to affect customers;
  • links to incident detail and customer action when available.

API process check

The machine-readable GET /api/v1/status response confirms that the current application process can answer a request and identifies API version v1. It is not a complete dependency check, uptime record, or SLA result. A successful process check does not prove that every provider or customer operation is available.

Incident communication

Verified incidents are published on the incidents page, which is limited to the trailing 30 days. Active paid customers affected by an incident receive email and a customer-panel notification when contact and delivery are available. Urgent updates may be corrected as facts become known.

For account-specific help, use the authenticated support section. For a public or pre-purchase question, use the contact page. Never include a complete API key, authentication token, or market value in a support message.

Availability commitment

Servix does not currently publish a contractual SLA, uptime percentage, or guaranteed support-response time. This page reports operational communication and must not be interpreted as a historical availability calculation.

Operational references

Read recent incidents, API changes, and support guidance