Live

Maintenance in the Zürich, Switzerland data center

MaintenanceOfficial update

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The latest update from Kinsta.

State

In progress

Started

Ongoing for

1 h 53 min

Worst impact

Maintenance

Timeline

2 updates
03:0003:2803:5604:2404:53
MaintenanceUpdate postedTimes in UTC

Scheduled

1 min 0%

In progress

1 h 53 min 100%

Updates

Times in UTC

As posted by Kinsta

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

We are performing server maintenance (server reboot) in the Zürich, Switzerland data center. Sites will be unavailable for 5 to 15 minutes during the daily maintenance window (between 2 a.m. and 5 a.m. local time). We don't expect any issues as a result of the maintenance, but please let our support team know if your sites experience anything unexpected after maintenance is complete.

Affected components

1
Zürich, Switzerland data centers

Kinsta in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

12

Days with an incident

26

Median duration

6 h 26 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 days
median 6 h 26 min
90 days agoToday

Other Kinsta incidents

All incidents

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=kinsta
Slack
/feed subscribe https://outages.live/feed.xml?providers=kinsta

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane