CHYP.ai · ORBIT // Cloudy_Day Security Suite

Databases & data

Operational Supabase status

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

FROM ALL SOURCES

Supabase looks fine itself, but Amazon Web Services, a provider it may run on (inferred), reports major outage. Watch for knock-on effects.

confidence: low Vendor: operational · users: normal · routing: no data · upstream providers: major.

Vendor status vs. reality: Vendor status and outside signals roughly agree
The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started14 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 “Increased Errors with Project Lifecycle Operations in US-West-2”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low
  • Amazon Web Services reports an issue. Supabase may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low

What we don't know: what is happening inside Supabase'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.

Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.

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 · upstream providers: major. Vendor status and outside signals roughly agree.

Who depends on whom

Supabase may run on Amazon Web Services (inferred). We don't map other services that depend on Supabase. 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

Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Supabase 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

The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.

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

INCIDENT REPLAY

Increased Errors with Project Lifecycle Operations in US-West-2

minor resolved · started · resolved

4 updates

  1. identified

    All Project Lifecycle operations are currently impacted by an upstream provider incident affecting EC2 instances in US-West-2. Currently up and active projects are unaffected and remain healthy. New project creation, unpauses, restore actions, project size changes, restarts and other lifecycle operations may encounter errors. We advise against taking these actions in US-West-2 at this time while we work with our provider to resolve this issue.

  2. identified

    We continue to work with our upstream provider as they investigate the ongoing incident affecting US-West-2. There are no additional updates at this time, and Project Lifecycle operations remain impacted. Currently active projects remain unaffected. We will provide another update in 2 hours, or sooner if additional information becomes available.

  3. monitoring

    Our upstream provider has implemented changes, and we are seeing recovery in project creation in US-West-2. We will continue to monitor the recovery of Project Lifecycle operations to ensure stability.

  4. resolved

    The upstream provider incident has been resolved, and Project Lifecycle operations in US-West-2 have recovered. All operations are functioning normally, and we are marking this incident as 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