Start free trial

Operations · Public status

System status.

Current operational status of ASOLOOP surfaces, plus the policy governing maintenance windows and incident communication. This page is updated manually during the early-production phase; a third-party status surface is on the roadmap.

Last checked: 2026-06-02

99.9%

Monthly uptime target for Teams — see the SLA

Current status

All systems operational

Components

Per-component status, maintained by hand and reviewed on each deploy — ASOLOOPdoes not yet run per-component synthetic probes, so treat this page as a statement of record rather than a live feed. What is automated today: an API health endpoint and a two-hourly worker deadman that alerts on a missed scheduled run. Upstream provider components are tracked for transparency but excluded from the SLA per § 4 Exclusions.

  • Marketing site

    Public marketing surface at https://asoloop.com.

    Operational

  • Application

    Product application at https://app.asoloop.com — workspace, recommendations, programs, settings.

    Operational

  • HTTP API

    Programmatic surface (read-only at Pro+; write + webhooks at Teams).

    Operational

  • Billing

    Stripe-backed subscription billing, invoicing, dunning. Outages here may delay invoice delivery but do not affect application access.

    Operational

  • MMP integrations

    AppsFlyer, Adjust, Branch, and Firebase Analytics — all four connectors live; operator-controlled connection for revenue-denominated confidence.

    Operational

  • App store APIs

    Apple App Store Connect API + Google Play Console API ingestion via operator-authorised credentials. Upstream provider outages are tracked but excluded from ASOLOOP uptime per SLA.

    Operational

Maintenance policy

  • Scheduled maintenance is announced at least 24 hours in advance via this page and via email to Workspace Owners on Pro and Teams tiers.
  • Maintenance is scheduled during low-traffic windows (Sundays 06:00–10:00 UTC by default; alternative windows negotiable for Teams customers in the executed agreement).
  • Scheduled maintenance is excluded from SLA uptime calculation per the SLA.
  • Emergency maintenance for security or stability is announced at the moment of execution and reported in the post-incident summary.

Incident history

No reportable incidents in the current month or the trailing 90 days.

During early production, full incident history begins at first paying-customer GA. Pre-traction operational events are not retroactively reported here; future incidents will appear chronologically with root cause, customer impact, remediation, and preventive measures per the security incident-response policy.

Subscribe to status updates

Email notifications for incidents and maintenance windows are sent automatically to all Workspace Owners on Pro and Teams tiers. To subscribe a non-Owner email address (e.g., a shared on-call alias, an internal procurement contact), send a request to support@asoloop.com with subject line [status] notifications.

A public RSS / webhook feed and a third-party status-page integration (statuspage.io / instatus / BetterStack) are on the V1 GA roadmap.

See also: SLA · Security · Changelog · Contact