CHYP.ai · ORBIT // Cloudy_Day Security Suite

APIs: messaging, media, analytics

Operational Mixpanel status

mixpanel.com · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

No sign of a widespread Mixpanel problem right now; every source we read is quiet.

confidence: medium Vendor: operational · users: normal · routing: no data.

Vendor status vs. reality: Vendor status and outside signals roughly agree

Regions mentioned: Application Availability (US)

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started86 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: postmortem on “Degraded Query API Performance impacting US Projects”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low

What we don't know: what is happening inside Mixpanel's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “postmortem”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.

Who depends on whom

Mixpanel may run on Google Cloud (inferred). We don't map other services that depend on Mixpanel. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Mixpanel or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Mixpanel may depend on.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Mixpanel. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

Degraded Query API Performance impacting US Projects

major postmortem · started · resolved

5 updates

  1. investigating

    Mixpanel is experiencing degraded Query API performance, resulting in HTTP 500 responses when querying reports for projects with US Data Residency. Projects with EU and IN Data Residency remain unaffected. We appreciate your patience while our engineers work to restore normal functionality. We will post progress updates on our status page. If you have any questions, please <a href="https://mixpanel.com/get-support">contact support.</a>

  2. identified

    The issue has been identified and a fix is being implemented.

  3. monitoring

    A fix has been implemented, and we're seeing improved success rates for the Query API. We will continue monitoring to ensure stability.

  4. resolved

    This incident has been resolved.

  5. postmortem

    # Mixpanel RCA: Temporary Query Service Disruption for US Projects August 26, 2026 # Summary Between approximately **2:02 PM and 3:19 PM PT on August 26, 2026**, projects in the US region experienced failures loading reports and running queries through the Mixpanel UI and Query API. During this window, some queries in the region failed or returned errors. **No customer data was lost, and data ingestion was not affected.** All events continued to be collected and stored normally throughout the incident; once query service was restored, all reports reflected complete, accurate data with no customer action required. The cause was identified as a recently deployed internal tool for diagnostic query replay, a capability our engineers use to re-run copies of past queries to debug performance, which unexpectedly wrote large amounts of data to the disks of our query servers, consuming storage ca

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next