Status Page

Real-time service status

Max Socials publishes live uptime and incident data at status.maxsocials.com. That page is updated automatically; you do not need to contact support to determine whether a degradation is platform-wide or isolated to your account.

The status page is hosted independently of the Max Socials application stack, so it remains accessible during platform incidents.

Monitored services

Every component below has a dedicated check on the status page. Per-source and per-channel granularity lets you see exactly where an issue is without reading a vague "some services affected" banner.

Web application

app.maxsocials.com, dashboard, review queue, brand settings, and user management
api.maxsocials.com, REST API and webhook delivery endpoints

Discovery ingestion (per source)

RSS feed crawlers
Reddit signal collector
X (Twitter) trend ingestion
TikTok trend ingestion
Google Trends poller

Each source is checked independently. A disruption to X ingestion does not affect Google Trends or RSS collection.

Production engines

Text engine, AI copy generation for all channels
Image engine, AI image generation and resizing
Video engine, script-to-video rendering (Remotion pipeline)

Distribution checks verify both the scheduler queue and the downstream platform API. If Instagram's API is returning errors, only the Instagram row shows degraded; all other channels continue posting normally.

Supporting systems

Analytics ingestion, organic and paid performance data collection
Webhook delivery, outbound event delivery to customer endpoints

Incident severity definitions

Every incident is classified at one of four levels. The level determines how we communicate and how fast we escalate.

Operational. All checks passing. No user impact. 100% functional.
Degraded. Partial impact on one or more components. A workaround is available. Performance may be slower than normal but the service is completing requests.
Partial outage. One or more services are fully down. Other services continue to operate. Affected functionality is unavailable until resolved.
Major outage. Multiple core services are down simultaneously. Broad user impact. Engineering is in active incident response.

Incident history

The public status page retains a rolling 90-day incident history. Every resolved incident includes a timeline and a summary of what happened.

For incidents that breached SLA thresholds, a full post-mortem is published in the Changelog and emailed to affected accounts. Post-mortem records are retained indefinitely.

Subscribe to alerts

From the status page you can subscribe to incident notifications by:

Email, receive a message when any component changes state and again when the incident resolves
RSS, add the status feed to any RSS reader or Slack workflow for team-wide visibility

Subscriptions are scoped per component, so you can follow only the channels or engines that matter to your workflow.

Service level targets

Uptime commitments are tier-dependent and measured as a monthly rolling window across all monitored services:

Growth and Agency tiers, 99.9% monthly uptime target
Enterprise tier, 99.95% monthly uptime target, backed by a contractual SLA with credit provisions

Scheduled maintenance windows are announced at least 48 hours in advance on the status page and excluded from SLA calculations. Enterprise customers may request maintenance windows outside business hours.