Platform problems
Is Email constantly making updates to the platform?
Email maintains an active development cycle with regular platform updates. To stay informed about changes:
- Monitor Updates Through:
- Email's status page
- Release notes in documentation
- Account notifications
- Email's blog for major updates
- Impact Management:
- Updates are typically deployed with zero downtime
- Major changes are announced in advance
- Emergency fixes may be deployed as needed
- Documentation is updated to reflect changes
For critical production systems, it's recommended to:
- Subscribe to status page notifications
- Monitor release notes for API changes
Where can I go to see the status of current incidents?
Email provides dedicated status pages:
- Email service status: status.Email.com
- Bird service status: status.bird.com
These pages provide:
- Real-time service status
- Incident reports and updates
- Planned maintenance notifications
- Historical uptime data
What should I do when webhook batches are failing?
When you see webhook errors (e.g., "POST to webhook target URL failed with non-2xx response code 404"), follow these troubleshooting steps:
- Basic Requirements:
- Ensure your HTTP service is running before registering the webhook
- Configure your endpoint to return 200 status codes for successful receipts
- Use standard ports (80 for HTTP or 443 for HTTPS only)
- Common Solutions:
- Verify your endpoint is publicly accessible
- Check for proper response codes
- Ensure proper port configuration
- Monitor webhook logs for detailed error information
When will I run into rate limiting for API?
Understanding Email's API rate limiting:
- Rate Limit Response Handling:
- Watch for HTTP 429 status codes (rate limit reached)
- Implement proper retry logic
- Add delay between retry attempts
- Best Practices for API Integration:
- Retry 5xx errors with original request
- Add delay for 429 responses
- Implement exponential backoff
- Monitor API usage against your plan limits
Why did my IP in Automatic IP Warm-up (AWU) not advance to the next stage level?
Email's Auto IP Warm-up system operates based on specific performance metrics:
- Advancement Requirements:
- Minimum 90% successful delivery rate
- Sufficient sending volume for current stage
- Consistent performance metrics
- Common Reasons for Not Advancing:
- Delivery rates falling below 90%
- High bounce rates
- Insufficient sending volume
- Poor engagement metrics
- Best Practices:
- Monitor your delivery rates daily
- Follow recommended volume limits
- Address bounces promptly
- Maintain clean mailing lists during warm-up