Current status
All core beta services are currently operational.
Status
System Status
OobiMax system health for the operator path that matters: connect, map, review, approve, deliver, recover, and learn.
What is monitored
- application availability and data collection cycles
- Refresh Intelligence and Signal Watch
- Google Ads, Meta Ads, and TikTok Ads integration paths
- exact-campaign Optimization Plans, Change Set approval, and guarded execution services
- Retry Execution recovery path
- Policy & Evidence Center review records for campaign policy triage and no-spend safeguards
- higher-tier Campaign Builder creative intake, editable plans, and no-spend safeguards
- Campaign Plans, Change Sets, and earlier Slack/Telegram mirror compatibility
- Workspace Readiness for media setup and Measurement Signals readiness
- approved read-only GA4/Search Console Measurement consent, discovery, and aggregate evidence safeguards
- Results Dashboard by Business Goal and Platform Setup
- measurement evidence explanations for budget or learning-sensitive actions
- transactional email delivery
- legacy Slack and Telegram callback rejection so retired recommendation actions fail closed
Beta readiness focus
During controlled beta, status focuses on source connection, account discovery, brand mapping, Campaign Plan quality, approval safety, execution recovery, Results accuracy, and Campaign Builder readiness where enabled.
Plan and change safety
A Campaign Optimization Plan explains one exact campaign. Only actions selected into a Change Set can move toward approval and supported execution.
- Campaign Plans are the primary analysis surface
- Change Sets are the approval boundary for supported actions
- Earlier Slack and Telegram recommendation cards remain immutable history and cannot be used as a current action surface
- measurement evidence can support review, but hints, stale evidence, or missing evidence never approve creation, launch, resume, budget, or spend
- already-handled decisions return canonical status instead of executing twice
- surface QA scripts flag thin cards, confusing action language, or missing action detail
Incident handling
In the event of degraded performance or outages, updates will be published here.
Support
support@oobimax.io