CHYP.ai · ORBIT // Cloudy_Day Security Suite

Identity, access & networking

Operational Clerk status

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

FROM ALL SOURCES

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

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

Vendor status vs. reality: Vendor status and outside signals roughly agree
The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started22 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 “SMS Delivery Issues”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low
  • Cloudflare reports an issue. Clerk may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low

What we don't know: what is happening inside Clerk'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: minor. Vendor status and outside signals roughly agree.

Who depends on whom

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

Identity & trust lens

When Clerk has trouble, people see failed logins, MFA prompts that don't arrive and sessions that drop. That's when phishing pages and “verify your account” texts show up. Only sign in through the official app or site, and don't re-enter credentials from a link someone sends you.

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 Clerk 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 Clerk may depend on.

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

INCIDENT REPLAY

SMS Delivery Issues

major resolved · started · resolved

6 updates

  1. investigating

    We’re investigating SMS delivery issues affecting some users. Verification codes may be delayed or fail to arrive.

  2. investigating

    We’re investigating SMS delivery issues with an upstream SMS provider.

  3. investigating

    We're continuing to investigate SMS delivery issues with an upstream vendor impacting users on AT&T.

  4. investigating

    We’ve identified an issue with an upstream SMS provider’s delivery route to AT&T numbers. The provider is switching traffic to an alternate route. We’re monitoring delivery rates and will share updates as we learn more.

  5. monitoring

    SMS verification completion rates have returned to normal levels following the provider’s switch to an alternate delivery route. We’re continuing to monitor delivery and verification rates.

  6. resolved

    The SMS delivery issue is resolved. Delivery and verification completion rates have returned to normal following our upstream provider’s switch to an alternate route.

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