Email Alerts
Email is the default notification channel and requires no external configuration.
Adding an Email Channel
- Go to Settings → Notification Channels
- Click New Channel
- Select Email
- Enter one or more email addresses (comma-separated)
- Click Save
- Click Test to verify delivery
Email Format
DOWN notification:
Subject: 🔴 DOWN: Production API Health — pingsla.com
Your monitor "Production API Health" is DOWN.
URL: https://api.yourapp.com/health
Reason: HTTP 503 Service Unavailable
Since: 2026-05-18 14:32:00 UTC
Region: us-east-1, eu-west-1
View incident: https://app.pingsla.com/incidents/inc_xxxxxxxxx
RECOVERED notification:
Subject: ✅ RECOVERED: Production API Health — pingsla.com
Your monitor "Production API Health" has recovered.
URL: https://api.yourapp.com/health
Downtime: 4 minutes 22 seconds
Resolved: 2026-05-18 14:36:22 UTC
View incident: https://app.pingsla.com/incidents/inc_xxxxxxxxx
Multiple Recipients
Email channels support multiple addresses:
ops@yourcompany.com, cto@yourcompany.com, oncall@yourcompany.com
All addresses receive the same notification simultaneously. If you need different people to receive alerts at different severity levels, create separate alert policies with separate email channels.
Email Delivery
PingSLA sends email via dedicated transactional infrastructure (not shared SMTP). Emails originate from alerts@pingsla.com.
- SPF:
v=spf1 include:_spf.pingsla.com ~all(configured on pingsla.com) - DKIM: Signed with pingsla.com key
- DMARC: Aligned
tip
Add alerts@pingsla.com to your email allowlist to prevent alerts from landing in spam.
Troubleshooting
| Issue | Resolution |
|---|---|
| Alerts going to spam | Add alerts@pingsla.com to your allowlist |
| Not receiving test email | Check spam folder; verify address spelling |
| Delayed delivery | Email delivery is generally < 60 seconds; delays may indicate receiving server issues |