Service disruption at the Toronto (CA) data center
Service has remained stable in the Toronto (CA) data center. This issue is now resolved. If you are still seeing issues with your website please contact our support team. Thank you for your patience and we do apologize for any disruption to your business.
The latest update from Kinsta.
State
Resolved
Started
66 d ago
2026-08-27 16:43 UTC
Lasted
5 h 31 min
until 2026-08-27 22:14 UTC
Worst impact
Partial outage
Timeline
9 updatesInvestigating
37 min 11%
Identified
3 h 51 min 70%
Monitoring
1 h 3 min 19%
Updates
Times in UTCAs posted by Kinsta
Service has remained stable in the Toronto (CA) data center. This issue is now resolved. If you are still seeing issues with your website please contact our support team. Thank you for your patience and we do apologize for any disruption to your business.
Our Engineers have implemented a solution. We are now monitoring the service to ensure its ongoing stability. We appreciated your patience and apologize again for the disruption this caused. If you do have any questions or are continuing to see any issues please do not hesitate to contact our Support team.
Our Engineers are continuing to work on a solution. We appreciate your continued patience. If you do have any questions please do not hesitate to contact our Support team.
Our team is continuing to work on implementing a solution. We appreciate your continued patience. If you do have any questions please do not hesitate to contact our Support team.
Our team is continuing to work on implementing a solution. We appreciate your continued patience. If you do have any questions please do not hesitate to contact our Support team.
Our Engineers are continuing to work on a solution. We appreciate your continued patience. If you do have any questions please do not hesitate to contact our Support team.
Our team is working on implementing a solution. We appreciate your patience and apologize for this disruption. If you do have any questions please do not hesitate to contact our Support team.
Our engineers are continuing to work towards a solution. We appreciate your patience and apologize for this disruption. If you do have any questions please do not hesitate to contact our Support team.
Our Engineers are investigating reports of a service disruption affecting sites in the Toronto (CA) data center. We are working to restore service to affected sites as quickly as possible.
Affected components
1Follow 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