Lettermint incident

Intermittent increased latency and error rate

Minor Resolved View vendor source →
Started
Mar 05, 2026, 11:11 AM UTC
Resolved
Mar 05, 2026, 11:11 AM UTC
Duration
Detected by Pingoru
Mar 05, 2026, 11:11 AM UTC

Affected components

Lettermint websiteIncomingTeam APILettermint UISMTP RelaySending API

Update timeline

  1. investigating Mar 05, 2026, 09:26 AM UTC

    Status: Investigating We are investigating possible issues related to accessing Lettermint services. Updates will be shared as soon as we know more. Affected components Sending API (Partial outage) Team API (Partial outage) Incoming (Partial outage) SMTP Relay (Partial outage)

  2. monitoring Mar 05, 2026, 09:40 AM UTC

    Status: Monitoring We are monitoring the situation following an infrastructure node failure in one of our availability zones. Read database queries experienced degradation for approximately 72 seconds between 09:21–09:23 UTC impacting authentication during email submission and other endpoints. Write operations and cache services were unaffected throughout. All services have fully recovered. Affected components SMTP Relay (Operational) Sending API (Operational) Team API (Operational) Incoming (Operational)

  3. identified Mar 05, 2026, 10:07 AM UTC

    Status: Identified We have received an update to the cause of this incident, which is in fact not related to a node hardware failure as previously thought. Our cloud provider has accidentally triggered a rolling replacement of all cluster nodes in our EU-West region. This process is ongoing and may cause intermittent latency spikes or brief errors as workloads migrate and failover between nodes. Impact should be minimal. Our team is in contact with our cloud provider to receive updates on the resolution. We will provide updates as the situation develops. Affected components Lettermint UI (Degraded performance) Lettermint website (Degraded performance) Sending API (Degraded performance) Team API (Degraded performance) Incoming (Degraded performance) SMTP Relay (Degraded performance)

  4. monitoring Mar 05, 2026, 10:22 AM UTC

    Status: Monitoring Our cloud provider confirmed the roll-out was stopped. We are also no longer observing any more nodes being replaced for the last 30 minutes. All services are healthy again and we will keep monitoring the situation. Affected components Lettermint UI (Operational) Lettermint website (Operational) Sending API (Operational) Team API (Operational) Incoming (Operational) SMTP Relay (Operational)

  5. resolved Mar 05, 2026, 11:11 AM UTC

    Status: Resolved No more regressions have been noticed and all services are still healthy. Incident has been resolved. A follow-up from our cloud provider is still expected and we are taking measures to prevent issues like this in the long-term. Affected components SMTP Relay (Operational) Lettermint UI (Operational) Lettermint website (Operational) Sending API (Operational) Team API (Operational) Incoming (Operational)

Looking to track Lettermint downtime and outages?

Pingoru polls Lettermint's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Lettermint reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Lettermint alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Lettermint for free

5 free monitors · No credit card required