CHYP.ai · ORBIT // Cloudy_Day Security Suite

Hosting & PaaS

Operational Kinsta status

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

FROM ALL SOURCES

No sign of a widespread Kinsta 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

Regions mentioned: MyKinsta, Outbound Email System

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started3 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 “MyKinsta service disruption”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low
  • Cloudflare reports an issue. Kinsta may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low

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

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

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

INCIDENT REPLAY

MyKinsta service disruption

minor resolved · started · resolved

11 updates

  1. investigating

    Our Engineers are investigating reports of performance issues with our control panel, MyKinsta, particularly surrounding actions failing, such as changing PHP versions and pushing environments. We are working on restoring normal service to MyKinsta as quickly as possible.

  2. identified

    We have identified that this issue also impacts transactional email sent through WordPress. Our Engineering team has identified the issue and is working to restore normal service to both MyKinsta and WordPress transactional email delivery. We will continue to provide updates as they become available.

  3. identified

    Our Engineering team is continuing to work on a solution for this. We apologise for the ongoing disruptions.

  4. identified

    Our Engineering team have resolved the issue impacting transactional email. They are continuing to work on the issue impacting MyKinsta.

  5. identified

    MyKinsta will experience periods of intermittent availability as we work on deploying a fix.

  6. identified

    Site creation is temporarily down. We are investigating the best course of action to bring the services back online as soon as possible.

  7. identified

    SSH access and site creation are temporarily down. We are investigating the best course of action to bring these services back online as soon as possible.

  8. identified

    Our team is actively investigating this incident and will share updates as new information becomes available. SFTP access is also affected by this incident. Thank you for your continued patience.

  9. identified

    Our team is actively investigating this incident and will share updates as new information becomes available. SFTP access is also affected by this incident. Thank you for your continued patience.

  10. identified

    The Site Creation is now functional, we're working on restoring the full functionality to Mykinsta.

  11. 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