Service status

status.vaartix.com shows whether each part of Vaartix is working right now, with past incidents. It is checked from outside our servers every few minutes.

Components

Component	What it covers
Email sending	Emails you send through the API go out.
SMTP relay	smtp.vaartix.com accepts connections on ports 465 and 587.
Email events	Delivered, bounced and complained events are recorded, so email statuses and the dashboard stay current.
Webhooks	Events reach your webhook endpoints.
API	api.vaartix.com answers.
Dashboard	app.vaartix.com loads.
Website and Docs	vaartix.com and these docs load.

Degraded or down

• Degraded means it works, but slower than usual. For example, when Amazon SES asks us to slow down, sending is degraded: your emails are accepted and queued, and they go out as soon as SES allows. Nothing is lost.
• Down means it isn’t working. Emails you send are still accepted and queued, unless the API itself is down. They go out once sending recovers.

Webhooks is about our delivery, not your endpoint. If your endpoint answers with an error or times out, that shows in your webhook delivery log, not on the status page.

Health endpoints

The status page calls these public endpoints. You can monitor them yourself too. Each answers 200 when the component works, and 503 with a short reason when it doesn’t:

GET https://api.vaartix.com/health/sending

HTTP/1.1 503 Service Unavailable
{ "status": "degraded", "reason": "Sending is slowed down by Amazon SES. Emails are queued and will go out." }

Endpoint	Component
/health	API
/health/sending	Email sending
/health/smtp	SMTP relay
/health/events	Email events
/health/webhooks	Webhooks

status is ok, degraded or down. The answers are cached for up to a minute and never include account data. They aren’t part of the versioned API, so their wording can change.

Something wrong that the status page doesn’t show? Contact support.