Welkin Health Status Page

May 25, 2026 · resolved May 25

Dear Customers, We received notification from Mailgun of delayed email sending in their EU infrastructure today. We use Mailgun for email delivery in our platform. The issue has been resolved as of 08:55 PDT. Timeline - 05:18 PDT – Mailgun began investigating the issue. - 06:00 PDT – A fix was implemented and Mailgun began monitoring results. - 07:46 PDT – The issue was identified and a fix was being implemented. - 08:45 PDT – A fix was implemented and Mailgun resumed monitoring. - 08:55 PDT – The incident has been fully resolved. Details https://status.mailgun.com/incidents/xdlnv85rl42x We value our relationship and are committed to working with you and your clients to address any concerns. Thank you, The Welkin Team

Feb 11, 2026 · resolved Feb 11

Dear Welkin Customers, The earlier infrastructure incident impacting login access across Care, Admin, and Designer environments has now been resolved. You should now be able to access Welkin normally. Please check your access and let us know if you continue to experience any issues or notice anything unusual. Thank you for your patience and understanding. Welkin Support Team

Oct 20, 2025 · resolved Oct 21

Amazon Web Services (AWS) has resolved the earlier outage that affected multiple services, primarily in the US-EAST-1 region. All systems are now operating as usual. Our team continues to monitor performance closely, but no further impact is expected. You can view the current AWS status here: https://health.aws.amazon.com/health/status

Oct 3, 2025 · resolved Oct 9

The issue affecting secure emails sent via Paubox has been resolved. Paubox had introduced an unexpected change to the timestamp format returned by their service, which caused certain date fields in Welkin to appear invalid. Our team has implemented a fix to correctly handle the updated format, and all affected timestamps have been corrected. Impact: Date information for emails sent via Paubox is now displaying properly. No other Welkin services were impacted.

Jun 12, 2025 · resolved Jun 13

This incident has been resolved.