Resources

Status

Service availability and incidents

The single source of truth for service availability is the live status page. Bookmark it; subscribe for incident-only email or RSS updates.

Status page: status.openpost.so

What the status page covers

  • API — core /v1/* endpoints.
  • Publisher — the service that actually posts to social platforms.
  • Dashboard — the web UI.
  • Webhooks — outbound event deliveries.
  • Media pipeline — uploads and transcoding.
  • Per-platform connectors — one row per platform. Often the upstream is what’s down, not us.
When a platform like X or LinkedIn has an API outage, publishing to that channel fails for everyone, including OpenPost. We show it on the status page under the platform’s row and queue your posts for retry once they’re back up.

Uptime targets

API

99.95%

Publisher (best effort)

99.9%

Dashboard

99.9%

Historical uptime

Published monthly on status page

Subscribing to incidents

  • Email — Subscribe button on status.openpost.so
  • Slack — /statuspage subscribe status.openpost.so
  • RSS — https://status.openpost.so/history.rss
  • Webhooks — incident webhook deliveries into any endpoint you own

Incident severity

  • Major— publishing is broken or dashboard is down. Paging on-call, status page + email + Slack updates.
  • Minor— degraded performance, slow responses, partial functionality. Status page updates only.
  • Maintenance— scheduled, announced 7 days in advance. Off-peak only (weekends 02:00–06:00 UTC).

When to email support

If the status page is green and you’re still experiencing issues, email contact@infina.so with:

  • Your workspace ID (Settings → About)
  • Affected post or request IDs
  • What you tried, and what actually happened

It’s usually specific to your workspace — a disconnected integration, an expired token, a platform-specific policy. We’ll get you a fix within one business day.

Last updated April 2026 Edit this page