How to Manage MyKinsta Notifications

MyKinsta sends several types of notifications to keep you informed about your account, your invoices, and your website uptime. Managing these settings means you get the alerts that matter (site downtime warnings and resource limit alerts, for example) without being overwhelmed by email you do not need. All notification preferences are controlled from a single tab in your account settings.

How to Access Notification Settings in MyKinsta

1. Log into your MyKinsta account
2. Navigate to the lower-left corner of the screen and select User Settings
3. Click the Notifications tab

You will see a list of notification categories, each with a toggle to enable or disable it. Changes save automatically when you toggle each option.

Notification Types in MyKinsta

Overall Notifications

Sends an alert when your account approaches a plan limit. Kinsta will notify you when you have exceeded 80% of your disk space, monthly visits, or bandwidth allowance. Recommended: on: these alerts give you enough lead time to upgrade before your site is affected.

Newsletter Subscription

A weekly email covering WordPress hosting tips, industry updates, and Kinsta product news. Recommended: personal preference. If you want to stay current with Kinsta features and WordPress hosting trends, keep this on. If you find the volume too high, turn it off without affecting any site or account functionality.

Invoice in Email

Delivers PDF invoices directly to your inbox each billing cycle. This option is only available to account users with billing rights. You can also access all past invoices in Company > Billing regardless of this setting. Recommended: on for account owners who need invoices for bookkeeping.

Beta Crew Participation

Notifies you when Kinsta is accepting testers for new or updated features before they go public. Recommended: on if you want early access to new tools. This is optional and has no impact on your live sites.

Site Monitoring

Sends alerts when your site has a critical issue that needs immediate attention. Events that trigger a site monitoring notification include:

• Site downtime: your site is returning errors or is unreachable
• DNS errors: your domain is not resolving correctly
• SSL errors: your SSL certificate has expired or failed to renew
• Resource limit warnings: your site is approaching PHP worker or memory limits

Recommended: on for all accounts. Site monitoring notifications are the most operationally important alerts MyKinsta sends. Turning these off means you may not know your site is down until a visitor tells you.

Which Notifications Should You Enable?

At minimum, keep Overall and Site Monitoring notifications active : these are the alerts that protect your site and your plan. Invoice notifications are useful if you manage billing directly. Newsletter and Beta Crew are optional and can be toggled on or off without any effect on your site’s operation.

How Kinsta Monitors Your Site Uptime

Kinsta checks every site on its network for availability at regular intervals. Understanding how that monitoring works helps set the right expectations about how quickly you will be alerted when something goes wrong.

Kinsta’s monitoring system checks each site approximately every minute. If a site fails to respond within the expected window, the system waits for a second consecutive check failure before triggering an alert. This two-check threshold prevents false positives from brief network blips or extremely short-lived timeouts. In practice, it means you will typically receive a downtime email within two to three minutes of an actual outage beginning, not within 60 seconds.

The alert email includes the site name, the type of event (downtime, SSL failure, DNS error, or resource warning), and the time the issue was first detected. For resource limit warnings, the email arrives when usage crosses 80% of the plan threshold, giving you a window to scale before the site starts degrading.

What Kinsta’s monitoring does not cover: it checks whether the site returns a successful HTTP response (usually a 200 status code), but it does not perform a content check. This means a site that returns a 200 but shows a broken page or a database error message will not trigger an alert. For that level of monitoring, consider a third-party tool like Better Uptime or UptimeRobot alongside Kinsta’s built-in alerts.

Kinsta also monitors SSL certificate expiry. Certificates are flagged before they expire, so you typically receive a warning with time to act rather than an alert after the fact. The Let’s Encrypt certificates Kinsta provisions renew automatically; an SSL alert usually means the auto-renewal failed because of a DNS or domain ownership verification issue.

Routing MyKinsta Alerts to Slack or External Tools

MyKinsta sends notifications by email only. There is no native Slack integration or webhook output built into the notification settings. However, you can route those notification emails to Slack or other tools using an intermediary:

Option 1: Slack Email Integration

Slack supports a dedicated email address per channel. Anything sent to that address appears as a Slack message. To set it up:

1. In Slack, right-click on the channel you want alerts to appear in and select Open channel details.
2. Go to Integrations > Send emails to this channel.
3. Slack provides a unique email address for that channel.
4. In MyKinsta, go to Company > Users and add a new user with the Slack channel email address. Set the role to the minimum required (Developer is fine for monitoring purposes). Enable Site Monitoring notifications for that user.

Downtime and SSL alerts will now arrive in that Slack channel as soon as MyKinsta sends the notification email. This requires the Slack plan to support email integration (available on Pro and above; not available on the free Slack plan).

Option 2: Zapier Email Parser

If you are on the free Slack plan or want more flexibility, Zapier can parse incoming emails and forward them to Slack, PagerDuty, Microsoft Teams, or any other platform:

1. Set up a Zapier account and create a Zap with Email by Zapier as the trigger.
2. Zapier provides a unique parser email address. Forward MyKinsta notification emails to this address (use a Gmail filter or a similar email forwarding rule).
3. Set the action to post to Slack, send a text via Twilio, or open a PagerDuty incident, depending on your alerting preferences.

This approach gives you full flexibility over routing and escalation. A basic Zapier account with one active Zap is free, which is enough for most users who just want downtime alerts in Slack.

How to Add Multiple Recipients for MyKinsta Notifications

By default, MyKinsta sends notifications to the email address tied to your account. To send site monitoring alerts or invoice emails to other people on your team, each person needs their own MyKinsta account with the appropriate role and their own notification preferences configured.

Add team members through Company > Users. Assign the Admin role for full access including site monitoring, or the Billing role for invoice-only access. Each user then configures their own notification toggles after logging in. There is no single setting to broadcast all alerts to multiple external addresses outside this user model.

What to Do When a Site Monitoring Alert Fires

When Kinsta uptime monitoring detects a problem, an alert email arrives within minutes of the issue starting. The email shows the site name and the type of event (downtime, SSL error, DNS failure, or resource warning). On receiving an alert:

1. Check from a different network: visit the site from a phone on cellular data or a VPN. This confirms whether visitors are affected or the issue is local to your connection.
2. Check MyKinsta: Kinsta resolves many infrastructure-level issues automatically. The alert may have cleared by the time you log in.
3. For SSL alerts: go to the SSL Certificate panel and attempt a manual renewal. Let's Encrypt certificates auto-renew, but domain ownership verification failures can interrupt the process.
4. For resource limit warnings: check your PHP worker usage under Site → Analytics and consider scaling the server or optimising the heaviest requests.
5. Contact Kinsta support via MyKinsta chat if the issue has not resolved within 10 minutes. Include the site name and the time the alert fired.

Troubleshooting: Not Receiving MyKinsta Alerts

If site monitoring or invoice alerts are not arriving, check these causes in order:

• Spam or junk folder: Kinsta sends notification emails from a @kinsta.com address. Add this domain to your email provider's allowlist if you have aggressive spam filtering.
• Notification toggle is off: revisit User Settings and confirm the relevant notification type is enabled. Toggles save automatically, but it is worth double-checking after a browser crash or accidental click.
• Wrong email address on the account: go to User Settings and confirm the email address matches your active inbox. If a team member changed it or set a role-based address, notifications go there instead.
• Account role restriction: invoice notifications only reach users with billing rights. A Developer-role user will not receive invoice emails by design. Adjust the role in Company > Users if needed.
• Kinsta infrastructure issue: in rare cases the alert email itself is delayed. If you suspect downtime but received no alert, check the Kinsta status page at status.kinsta.com directly.

Final Word: How to Manage MyKinsta Notifications

Managing your MyKinsta notification preferences takes less than a minute from User Settings > Notifications. Keep Site Monitoring and Overall notifications on so you are alerted to downtime and resource limits before they affect visitors. For full account security, also enable two-factor authentication on MyKinsta so alerts cannot be silenced by an attacker who gains access to your login. If a site monitoring alert fires and you need to investigate the cause, you can also enable WordPress debug mode from the Tools tab to identify the root cause. Read more about what MyKinsta offers in our Kinsta review.