- Notice history

All systems operational

Application - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 99.91%Mar · 99.89%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

API - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 99.86%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Monitoring - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Sandbox - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Third Party: Auth0 → Europe (PROD) → Auth0 User Authentication - Operational

Third Party: Google Cloud Platform → Cloud Spanner - Operational

Data Freshness - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Notice history

Mar 2025

API Downtime
  • Resolved
    Resolved

    We have experienced some API instability after a release. The issue was quickly identified and resolved.

API offline
  • Resolved
    Resolved

    This incident has been resolved. The outage has been caused by automatic Kubernetes infrastructure upgrade affecting available resources of our database servers. This has been now adjusted to accommodate the changes.

  • Investigating
    Investigating

    We are currently investigating this issue.

API offline
  • Resolved
    Resolved

    This incident has been resolved.

  • Investigating
    Investigating

    We are currently investigating this issue.

App is currently experiencing some issues
  • Resolved
    Resolved

    There was a bug in a beta feature that has been fixed, which fired off many error requests to our app server. The load was not handled properly which led to restarts, a fixed has been rolled out.

  • Update
    Update

    We have identified the problem and disabled the feature that was causing the issue - we are still investigating what the root cause is.

  • Investigating
    Investigating

    We are currently investigating the issue

Feb 2025

Application Downtime & High CPU Usage
  • Resolved
    Resolved

    The issue has been identified and fixed.

  • Investigating
    Investigating

    The application experienced intermittent downtime accompanied by a significant CPU usage spike. Initial reports indicated that the app was down, and further investigation revealed that synchronous Mixpanel requests (which was down at that point in time) were not being handled gracefully. This led to blocking calls, repeated retries, and oversized log entries. Additionally, a premature backend release introduced errors when fetching sidepanel entities.

Jan 2025

No notices reported this month

Jan 2025 to Mar 2025

Next