CHYP.ai · ORBIT // Cloudy_Day Security Suite

APIs: messaging, media, analytics

Operational Sanity status

sanity.io · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

No sign of a widespread Sanity 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: Studio

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started43 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: resolved on “Elevated listener latency and error rate impacting Studio loading”. 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 Sanity'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 “resolved”. 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

Sanity may run on Google Cloud (inferred). We don't map other services that depend on Sanity. 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 Sanity 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 Sanity may depend on.

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

INCIDENT REPLAY

Elevated listener latency and error rate impacting Studio loading

critical resolved · started · resolved

18 updates

  1. investigating

    We are currently investigating an issue where elevated listener latency may result in slower performance and lag within Sanity Studio for a subset of customers. Our team is actively working to identify the root cause and mitigate the impact. Issue starting around 9:10 UTC.

  2. investigating

    We are continuing to investigate this issue.

  3. investigating

    We are currently continuing to investigate the issue, while also rolling out mitigations.

  4. investigating

    We are continuing to investigate the issue. Additionally, there might be a slight delay in document publishes for "scheduled publishing" functionality.

  5. investigating

    We are currently continuing to investigate the issue, while also preparing to roll a set of mitigations.

  6. investigating

    We are continuing to investigate this issue.

  7. investigating

    We are continuing to investigate this issue.

  8. investigating

    We're continuing to investigate this issue. In the meantime, we've begun rolling out preliminary measures to mitigate its impact.

  9. investigating

    We're continuing to investigate this issue. And we are continuing rolling out preliminary measures to mitigate its impact.

  10. investigating

    We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact. "scheduled publishing" functionality confirmed unaffected by this incident.

  11. investigating

    We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact.

  12. investigating

    We're continuing to investigate this issue. And we are continuing to apply measures to mitigate its impact.

  13. identified

    The issue has been identified. We are continuing to apply fixes to mitigate its impact.

  14. identified

    We are continuing to apply fixes to mitigate the impact.

  15. identified

    We are continuing to apply fixes to mitigate the impact. No errors have been observed from the changes rolled out so far.

  16. monitoring

    A fix has been fully implemented and we are monitoring the results.

  17. monitoring

    We are continuing to monitor for any further issues.

  18. resolved

    This incident has been resolved.

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