If something feels off — campaigns not sending, dashboard sluggish, Artemis erroring — the first thing to check is the public status page. We publish every incident there, usually within minutes of detecting it.
Where to check status
Public status page: status.brandjet.ai
In-app banner: an orange or red banner appears at the top of the dashboard during active incidents affecting your workspace.
Twitter / X:
@brandjetstatusfor shorter incident notes.
What the status page shows
Overall system status (Operational, Degraded, Partial Outage, Major Outage).
Per-component status (Dashboard, Email Sending, LinkedIn Sending, Warmup, Artemis, MCP, API, Webhooks).
Active incidents with timestamps, affected components, and ongoing updates.
Historical incidents going back 90 days, with post-mortems for major ones.
Subscribe to updates
Click Subscribe on the status page to receive notifications via email, SMS, Slack, or RSS the moment an incident is opened or updated. We strongly recommend subscribing if you depend on BrandJet for production outreach.
What does an incident actually mean?
Operational — everything is functioning normally.
Degraded — some operations are slower than usual but succeeding. Sends may be delayed by a few minutes.
Partial Outage — a subset of users or features cannot operate normally. We list exactly what is affected.
Major Outage — the platform or a critical component is down. We update every 15 minutes minimum until resolved.
Is the platform down?
If the status page says Operational but you are seeing errors, it is likely a workspace-specific issue (account disconnected, quota hit, DNS error). Run through:
Look at the in-app banner — workspace-level warnings appear there.
Check Accounts → Email and Accounts → Social for red indicators.
Open the Activity log on the campaign in question and click a failed row for the specific error.
If everything looks fine to you but the symptom persists, open a ticket with the timestamp and any error text.
Scheduled maintenance
We schedule maintenance during low-volume hours (typically Saturdays 02:00 to 06:00 UTC) and post a banner at least 48 hours in advance. Maintenance windows usually take seconds of impact, not minutes.
Post-mortems
For any incident lasting more than 30 minutes or affecting more than 5% of customers, we publish a detailed post-mortem within 5 business days, including root cause, what we changed, and what we are doing to prevent a repeat. Linked from the historical incident on the status page.