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 page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Cloudflare: Degraded / minor incident
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Kinsta support system
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 4 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “MyKinsta Support System Unavailable”. 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 Support System Unavailable
critical resolved · started · resolved
5 updates
- investigating
Our support system is not currently available. We are working to resolve the issue as quickly as possible.
- identified
We have identified the issues as being caused upstream by our live chat provider, Intercom. We are continuing to monitor the situation and will post updates as they become available.
- identified
Intercom has updated their status page to reflect the outages: https://www.finstatus.com/us-hosting/incidents/01M7JWJJY3RSVWY208SZDTMK05. We are continuing to monitor the situation and will post updates as they become available.
- monitoring
We are observing normal operations again. We will continue to monitor the situation. If you are still having issues reaching our Support team in MyKinsta, please email support@kinsta.com
- resolved
We have continued to observe normal operations and will mark this incident as resolved. We do apologize for any difficulties you experienced attempting to reach our support team.
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.