Service disruption at the Northern Virginia (US East 4) data center
This has been resolved.
The latest update from Kinsta.
State
Resolved
Started
24 d ago
2026-10-08 14:42 UTC
Lasted
7 h 21 min
until 2026-10-08 22:03 UTC
Worst impact
Partial outage
Timeline
4 updatesInvestigating
1 h 56 min 26%
Identified
1 h 44 min 23%
Monitoring
3 h 42 min 50%
Updates
Times in UTCAs posted by Kinsta
This has been resolved.
A fix has been implemented and we are monitoring the results. If your site was affected and is still experiencing difficulties, please contact our support team via chat in MyKinsta, or by emailing support@kinsta.com.
We have identified the cause of the issue, and we are currently working on a fix.
Our Engineers are investigating reports of a service disruption affecting sites in the Northern Virginia (US East 4) data center. We are working to restore service to affected sites as quickly as possible.
Affected components
1Kinsta in the last 90 days
Full historyIncidents in 90 days
13
Days with an incident
29
Median duration
6 h 27 min
This incident
About the median
Other Kinsta incidents
All incidentsKinsta·Downloadable Backup actions are stuck in processing status in the MyKinsta Dashboard.
This incident has been resolved.
Kinsta·MFA emails not being sent for MyKinsta
Following continued monitoring, we can confirm that MyKinsta email functionality has been operating normally, with no further issues observed. If you are still experiencing issues, please email us at support@kinsta.com.
Kinsta·Information in regards to newly discovered PHP vulnerability CVE-2026-115560 (Oct 23, 2026)
We can confirm that the mitigations have been successful and no compromises have occurred as a result of this. If you have any other questions, please contact our support team at support@kinsta.com.
Kinsta·PHP Security Vulnerability Update
All sites are protected, the PHP security updates have been rolled out across the platform, and we have no evidence of any breaches related to this vulnerability.
Kinsta·Partial outage in London datacenter
The infrastructure has remained stable and this has been resolved.
Follow Kinsta
Your coding agent knows when Kinsta is down, and tells you when a failure is theirs, not yours. You can also get Kinsta incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "kinsta" and tell me if Kinsta has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=kinsta/feed subscribe https://outages.cc/feed.xml?providers=kinstaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane