Snapshot 25146
Normalized text
Scripts and page chrome removed; this is what change detection compares.
{
"incidents": [
{
"created_at": "2026-09-23T16:54:02Z",
"id": "01M37K0H3VNEW9170PRBWB0J55",
"impact": "critical",
"incident_updates": [
{
"body": "The affected services are operating normally, and we have completed the emergency maintenance. Message intake stopped during two short periods: 18:51–18:57 and 19:02–19:04 CEST. Some tracking requests failed, and webhook delivery was delayed during those periods. During the later emergency maintenance, some Sending API requests returned errors until about 20:04 CEST.\n\nWe have monitored the services after the maintenance and are marking this incident resolved. We are sorry for the disruption. \n\nWe will publish a public write-up after we confirm the full customer impact, cause, and follow-up actions.",
"created_at": "2026-09-23T20:01:52Z",
"display_at": "2026-09-23T20:01:52Z",
"id": "01M37XRF54KP49G9AE024ZPC6E",
"incident_id": "01M37K0H3VNEW9170PRBWB0J55",
"status": "resolved",
"updated_at": "2026-09-23T20:01:52Z"
},
{
"body": "Email submissions and message processing have resumed. We confirmed two short interruptions: 18:51–18:57 and 19:02–19:04 CEST. Some tracking requests failed and webhook delivery was delayed during those periods. Later, some Sending API requests returned errors; the last such error we observed was around 20:04 CEST. We are monitoring sending and processing, and we are still checking incoming mail, before we resolve this incident.",
"created_at": "2026-09-23T18:23:50Z",
"display_at": "2026-09-23T18:23:50Z",
"id": "01M37R4ZN6GMXH0EFF4ACEQMGG",
"incident_id": "01M37K0H3VNEW9170PRBWB0J55",
"status": "monitoring",
"updated_at": "2026-09-23T18:23:50Z"
},
{
"body": "We are performing emergency maintenance to increase capacity. Brief service interruptions may occur during this work. We will provide another update when the maintenance is complete and service is stable.",
"created_at": "2026-09-23T17:33:40Z",
"display_at": "2026-09-23T17:33:40Z",
"id": "01M37N9392ZGPYQP1JN90QTQ7W",
"incident_id": "01M37K0H3VNEW9170PRBWB0J55",
"status": "identified",
"updated_at": "2026-09-23T17:33:40Z"
},
{
"body": "We have identified an issue in the infrastructure that supports message processing. We are working to resolve it and will share another update when we have verified the result.",
"created_at": "2026-09-23T17:06:59Z",
"display_at": "2026-09-23T17:06:59Z",
"id": "01M37KR84G7RZ678Y66AX59SPZ",
"incident_id": "01M37K0H3VNEW9170PRBWB0J55",
"status": "identified",
"updated_at": "2026-09-23T17:06:59Z"
},
{
"body": "We are investigating service unavailable errors affecting multiple services.\n\nOur apologies for the inconvenience. We will share an update once we have more information.",
"created_at": "2026-09-23T16:54:02Z",
"display_at": "2026-09-23T16:54:02Z",
"id": "01M37K0H3VWB40QXR04SWS4NFJ",
"incident_id": "01M37K0H3VNEW9170PRBWB0J55",
"status": "investigating",
"updated_at": "2026-09-23T16:54:02Z"
}
],
"name": "Widespread platform outage",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-09-23T20:01:52Z",
"status": "resolved",
"updated_at": "2026-09-23T20:48:10Z"
},
{
"created_at": "2026-09-01T06:17:42Z",
"id": "01M1DSVJS7NA9V15MJ5T19R3FN",
"impact": "minor",
"incident_updates": [
{
"body": "This incident has been resolved. SMTP relay and API are operating normally again.\n\nWe have deployed further mitigation measures to prevent this incident from occurring again and are keeping a close eye.\n\nApologies for the inconvenience this has caused.",
"created_at": "2026-09-01T07:40:27Z",
"display_at": "2026-09-01T07:40:27Z",
"id": "01M1DYK392B4PJQ4GGBVWC5MGW",
"incident_id": "01M1DSVJS7NA9V15MJ5T19R3FN",
"status": "resolved",
"updated_at": "2026-09-01T07:40:27Z"
},
{
"body": "We have been made aware of this issue reoccurring again and are currently investigating.\n\nThe incident has already been mitigated by killing the affected pod. We will share an update once we know more.",
"created_at": "2026-09-01T07:05:38Z",
"display_at": "2026-09-01T07:05:38Z",
"id": "01M1DWKB832H6C87DEGSGJ8JJN",
"incident_id": "01M1DSVJS7NA9V15MJ5T19R3FN",
"status": "investigating",
"updated_at": "2026-09-01T07:05:38Z"
},
{
"body": "On September 1, between 04:01 and 04:06 UTC, one of our API instances returned errors for a small number of requests. Some customers sending email through our API or SMTP service might have seen a submission or authentication error. Other instances remained healthy, and most requests continued normally.\n\nNo email already accepted by Lettermint was lost. Failed requests stopped before we accepted or created the message, so clients could retry them after service recovery. A small number of email-open events might not have been recorded. No stored customer data was changed or exposed.\n\nThe cause was a defect in the PHP JIT. We already had a safeguard for this issue, but it did not cover this additional code path.\n\nWe expanded the safeguard and removed the affected date calculation from the application startup process. This lets us keep the performance optimisation active for the rest of the application. We will also install the permanent PHP fix when it becomes available in our production runtime which at the time of writing is not the case.\n\nWe continue to monitor the service. We are sorry for the disruption.",
"created_at": "2026-09-01T06:17:43Z",
"display_at": "2026-09-01T04:06:00Z",
"id": "01M1DSVJS7QBSP6F2RBXAWAQHS",
"incident_id": "01M1DSVJS7NA9V15MJ5T19R3FN",
"status": "resolved",
"updated_at": "2026-09-01T06:17:43Z"
},
{
"body": "We are investigating failing requests and retries affecting SMTP relay.",
"created_at": "2026-09-01T06:17:42Z",
"display_at": "2026-09-01T04:01:00Z",
"id": "01M1DSVJS717GCQ3Z9FZ8EDKBZ",
"incident_id": "01M1DSVJS7NA9V15MJ5T19R3FN",
"status": "investigating",
"updated_at": "2026-09-01T06:17:42Z"
}
],
"name": "API and SMTP relay degradation",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-09-01T04:06:00Z",
"status": "resolved",
"updated_at": "2026-09-01T07:40:27Z"
},
{
"created_at": "2026-08-11T08:03:41Z",
"id": "01KZQXJH4BV23Y5A40VEJKGPVX",
"impact": "minor",
"incident_updates": [
{
"body": "We have fully removed the affected IP address from active sending and traffic has been rerouted across our remaining broadcast infrastructure. Email delivery is operating normally again.\n\nThe affected IP will remain out of service while we continue working with Microsoft on the block. As this no longer impacts active sending, we are marking this incident as resolved.\n\nTransactional routes and other broadcast IPs remain unaffected.",
"created_at": "2026-08-12T08:13:16Z",
"display_at": "2026-08-12T08:13:00Z",
"id": "01KZTGGSNXY3NEH9DZA67SSM81",
"incident_id": "01KZQXJH4BV23Y5A40VEJKGPVX",
"status": "resolved",
"updated_at": "2026-08-12T08:15:33Z"
},
{
"body": "We have identified the source of the listing and are actively remediating the issue.\n\nWe will keep monitoring the situation.\n\nOur sincere apologies for the inconvenience.",
"created_at": "2026-08-11T08:24:18Z",
"display_at": "2026-08-11T08:24:18Z",
"id": "01KZQYR98JTBPS8C7PW99WQQCP",
"incident_id": "01KZQXJH4BV23Y5A40VEJKGPVX",
"status": "identified",
"updated_at": "2026-08-11T08:24:18Z"
},
{
"body": "We’ve identified that one of our outbound broadcast IP addresses have been blocklisted, affecting email delivery for some customers. The team is currently investigating the cause and working on delisting the IP. In the meantime, the IP address has been suspended and will not be used until the issue is resolved. This does not affect other IPs in the pool nor transactional routes.\n\nIf you have seen a hard bounce because of this, you can safely reactivate the recipient from your suppression management.\n\n ",
"created_at": "2026-08-11T08:03:41Z",
"display_at": "2026-08-11T08:03:41Z",
"id": "01KZQXJH4BW3Q08VFAS7NW7EER",
"incident_id": "01KZQXJH4BV23Y5A40VEJKGPVX",
"status": "investigating",
"updated_at": "2026-08-11T08:03:41Z"
}
],
"name": "[Blocklist] Broadcast IP blocked with Outlook OLC",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-08-12T08:13:00Z",
"status": "resolved",
"updated_at": "2026-08-12T08:13:16Z"
},
{
"created_at": "2026-07-23T11:19:59Z",
"id": "01KY7B89YJYP0RGHQ35YAC8F4Z",
"impact": "minor",
"incident_updates": [
{
"body": "The cloud provider outage has been resolved, and inbound emails and attachments can now be retrieved normally. We have not observed any further timeouts.",
"created_at": "2026-07-23T14:23:13Z",
"display_at": "2026-07-23T14:23:13Z",
"id": "01KY7NQTX9RFQMCSERTE1W6PXQ",
"incident_id": "01KY7B89YJYP0RGHQ35YAC8F4Z",
"status": "resolved",
"updated_at": "2026-07-23T14:23:13Z"
},
{
"body": "We are seeing elevated timeouts when accessing object storage due to an ongoing cloud provider outage. Our failover systems are operating as expected, but some requests may still time out. \n\nWe are monitoring the situation closely.",
"created_at": "2026-07-23T11:19:59Z",
"display_at": "2026-07-23T11:19:59Z",
"id": "01KY7B89YJWH8447WEZ3PFEQDE",
"incident_id": "01KY7B89YJYP0RGHQ35YAC8F4Z",
"status": "monitoring",
"updated_at": "2026-07-23T11:19:59Z"
}
],
"name": "Intermittent Timeouts Retrieving Inbound Emails and Attachments",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-07-23T14:23:13Z",
"status": "resolved",
"updated_at": "2026-07-23T14:23:13Z"
},
{
"created_at": "2026-07-15T15:26:15Z",
"id": "01KXK65G7HMXKGCBQ3G0DJKTZN",
"impact": "major",
"incident_updates": [
{
"body": "API availability has been fully restored and the platform has remained stable. We reverted a health-check configuration that reacted too aggressively to a brief traffic spike, causing healthy instances to be temporarily removed from service. We have confirmed normal operation and are reviewing additional safeguards to prevent a recurrence.",
"created_at": "2026-07-15T15:26:15Z",
"display_at": "2026-07-15T15:15:00Z",
"id": "01KXK65G7HYZ0PY0J6MFCGBQA3",
"incident_id": "01KXK65G7HMXKGCBQ3G0DJKTZN",
"status": "resolved",
"updated_at": "2026-07-15T15:26:15Z"
},
{
"body": "We experienced a brief period of API unavailability, during which some requests returned `503 Service Unavailable`. Multiple API instances temporarily became unresponsive at the same time, leaving insufficient capacity to serve requests.\n\nService has been restored and remains stable. We are monitoring closely and investigating what caused the instances to become unresponsive.",
"created_at": "2026-07-15T15:26:15Z",
"display_at": "2026-07-15T15:01:00Z",
"id": "01KXK65G7HZT4QWC8EKHA8D3PC",
"incident_id": "01KXK65G7HMXKGCBQ3G0DJKTZN",
"status": "monitoring",
"updated_at": "2026-07-15T15:26:15Z"
},
{
"body": "We are investigating an increase in 503 Service Unavailable responses.",
"created_at": "2026-07-15T15:26:15Z",
"display_at": "2026-07-15T15:00:00Z",
"id": "01KXK65G7H78QHSPB5H10YMGP2",
"incident_id": "01KXK65G7HMXKGCBQ3G0DJKTZN",
"status": "investigating",
"updated_at": "2026-07-15T15:26:15Z"
}
],
"name": "API availability issues",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-07-15T15:15:00Z",
"status": "resolved",
"updated_at": "2026-07-15T15:26:15Z"
},
{
"created_at": "2026-06-27T17:39:28Z",
"id": "01KW52MFAWC881G0QD72TGHN7S",
"impact": "minor",
"incident_updates": [
{
"body": "This incident has been resolved. We applied a fix and have confirmed that the dashboard and Team API are working normally, with no further errors.",
"created_at": "2026-06-27T18:05:08Z",
"display_at": "2026-06-27T18:05:08Z",
"id": "01KW543F9MGXTKFH9CTWCRSER4",
"incident_id": "01KW52MFAWC881G0QD72TGHN7S",
"status": "resolved",
"updated_at": "2026-06-27T18:05:08Z"
},
{
"body": "We are no longer seeing elevated error rates on the Team API or dashboard and functionality appears to have returned to normal.\n\nWe are continuing to monitor the situation closely to ensure stability, but no new errors have been observed since mitigation was applied.",
"created_at": "2026-06-27T18:01:10Z",
"display_at": "2026-06-27T18:01:10Z",
"id": "01KW53W6T5SN1QH7MG35M1C0EG",
"incident_id": "01KW52MFAWC881G0QD72TGHN7S",
"status": "monitoring",
"updated_at": "2026-06-27T18:01:10Z"
},
{
"body": "We are seeing increased error rates on the Lettermint dashboard and our Team API. Requests to the Team API and actions in the dashboard may fail or respond slowly while we look into this.\n\nEmail delivery is not affected. Transactional and broadcast messages are still being sent and processed as normal.\n\nOur team is investigating the cause and we will post an update shortly.",
"created_at": "2026-06-27T17:39:28Z",
"display_at": "2026-06-27T17:39:28Z",
"id": "01KW52MFAWQ1FBAZQSX1VEG6S6",
"incident_id": "01KW52MFAWC881G0QD72TGHN7S",
"status": "investigating",
"updated_at": "2026-06-27T17:39:28Z"
}
],
"name": "Increased error rates on the dashboard and Team API",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-06-27T18:05:08Z",
"status": "resolved",
"updated_at": "2026-06-27T18:05:08Z"
},
{
"created_at": "2026-06-26T21:21:06Z",
"id": "01KW2WXK6JXK2HJBRFVWC25S05",
"impact": "major",
"incident_updates": [
{
"body": "We resolved the API token authentication issue at 23:01 CEST by rolling back the change that introduced the failure.\n\nBetween approximately 22:56 and 23:01 CEST, a subset of API requests authenticated with tokens may have returned 500 errors when they required a fresh authentication lookup. Requests using already-cached token authentication continued to work.\n\nThe issue was caused by a database migration/deployment sequencing problem. The change introduced a new table for token authentication data and was designed to be backwards compatible: if no token data existed in the new table yet, authentication would fall back to the existing data source.\n\nThis fallback behavior worked as expected in development and staging. However, our staging environment did not reproduce the production migration timing. In production, the migration ran significantly longer because of the larger dataset and remained inside a transaction. Until that transaction committed, the newly-created table was not yet visible to the application. As a result, fresh token authentication lookups could fail before the intended fallback path was reached.\n\nIn other words, we accounted for missing data in the new table, but not for the table itself being temporarily unavailable during a long-running transactional migration.\n\nThis was our mistake. We tested the change and specifically designed it to avoid breaking existing authentication data, but our deployment safeguards did not adequately cover this failure mode.\n\nGiven the recent increase in production incidents, we are treating this as a high-priority reliability issue. We are pausing this rollout path and tightening our deployment process before reintroducing the change. In particular, we will separate schema changes from longer-running migration work, add explicit preflight checks for required database objects before enabling dependent code paths, and apply stricter rollout gates to authentication-related changes.\n\nAll affected services are currently operating normally.",
"created_at": "2026-06-26T21:21:06Z",
"display_at": "2026-06-26T21:01:00Z",
"id": "01KW2WXK6JZCVYZ5MCX4V23N13",
"incident_id": "01KW2WXK6JXK2HJBRFVWC25S05",
"status": "resolved",
"updated_at": "2026-06-26T21:46:06Z"
},
{
"body": "We are investigating an increase in 500 errors.",
"created_at": "2026-06-26T21:21:06Z",
"display_at": "2026-06-26T20:56:00Z",
"id": "01KW2WXK6J1XB41T7W5YMV1ZCW",
"incident_id": "01KW2WXK6JXK2HJBRFVWC25S05",
"status": "investigating",
"updated_at": "2026-06-26T21:21:06Z"
}
],
"name": "Elevated 500 errors with API authentication",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-06-26T21:01:00Z",
"status": "resolved",
"updated_at": "2026-06-26T21:21:06Z"
},
{
"created_at": "2026-06-23T08:39:16Z",
"id": "01KVST4FAGJ032309NN5EPA0BZ",
"impact": "none",
"incident_updates": [
{
"body": "We are not seeing anymore deferrals related to ratelimit for these IPs and will mark it as resolved.\n\nApologies for the inconvenience this has caused.",
"created_at": "2026-06-23T16:24:48Z",
"display_at": "2026-06-23T16:24:48Z",
"id": "01KVTMRWTD5T64JGTYNDB0WB83",
"incident_id": "01KVST4FAGJ032309NN5EPA0BZ",
"status": "resolved",
"updated_at": "2026-06-23T16:24:48Z"
},
{
"body": "We are seeing improvements and emails are being delivered.\n\nWe will keep monitoring the situation closely.",
"created_at": "2026-06-23T08:40:52Z",
"display_at": "2026-06-23T09:30:00Z",
"id": "01KVST7CV973SNWZGK3YPMGXC4",
"incident_id": "01KVST4FAGJ032309NN5EPA0BZ",
"status": "monitoring",
"updated_at": "2026-06-23T09:33:44Z"
},
{
"body": "We are actively mitigating this issue. You might see deferrals in your webhooks or UI instead of delayed processing. Please note emails are still being retried.\n\nThis is caused by an increase in volume due to the ongoing incident with Spamhaus listing, which is being resolved and the delisting is being propagated.\n\nThis issue does not impact Microsoft 365 (Outlook 365) addresses nor other providers.\n\nBroadcast is also not affected by the issue.\n\nOur sincere apologies for the inconvenience.",
"created_at": "2026-06-23T08:39:16Z",
"display_at": "2026-06-23T08:39:16Z",
"id": "01KVST4FAG8A75P8Z7N32CEPFF",
"incident_id": "01KVST4FAGJ032309NN5EPA0BZ",
"status": "identified",
"updated_at": "2026-06-23T08:39:16Z"
}
],
"name": "[Ratelimit] Delayed sending to Outlook OLC",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-06-23T16:24:48Z",
"status": "resolved",
"updated_at": "2026-06-23T16:24:48Z"
},
{
"created_at": "2026-06-23T06:01:42Z",
"id": "01KVSH3YBGW1G7CCETXV2RAJT5",
"impact": "none",
"incident_updates": [
{
"body": "We are not seeing anymore bounces related to the Spamhaus listing and are working on resending all impacted messages.\n\nDue to the length and impact of this incident we will share a post-mortem on this incident.\n\nApologies for the inconvenience this has caused.",
"created_at": "2026-06-23T16:24:12Z",
"display_at": "2026-06-23T16:24:12Z",
"id": "01KVTMQSG34T4B9BS36HMS9S67",
"incident_id": "01KVSH3YBGW1G7CCETXV2RAJT5",
"status": "resolved",
"updated_at": "2026-06-23T16:24:12Z"
},
{
"body": "We’ve been in contact with Spamhaus and the delisting process has now been successfully applied. The delisting has been put into effect, but mail providers that rely on Spamhaus may take some time to refresh and propagate these changes within their own systems and internal caches.\n\nWe are currently monitoring the situation closely while these updates continue to propagate. Once we determine that delivery has stabilized and it is safe to proceed, we will begin retrying affected emails that were not yet successfully delivered and provide further updates as needed.",
"created_at": "2026-06-23T15:14:56Z",
"display_at": "2026-06-23T15:14:56Z",
"id": "01KVTGRYYM6RJS6SHS5D1X1TQK",
"incident_id": "01KVSH3YBGW1G7CCETXV2RAJT5",
"status": "monitoring",
"updated_at": "2026-06-23T15:14:56Z"
},
{
"body": "We are still actively working on this issue and are awaiting an update from Spamhaus.\n\nWe will keep monitoring the situation.\n\nOur sincere apologies for the inconvenience.",
"created_at": "2026-06-23T13:38:18Z",
"display_at": "2026-06-23T13:38:18Z",
"id": "01KVTB80KP38BD0QF4XAHW0P9C",
"incident_id": "01KVSH3YBGW1G7CCETXV2RAJT5",
"status": "identified",
"updated_at": "2026-06-23T13:38:18Z"
},
{
"body": "We are still actively working on this issue and are awaiting an update from Spamhaus.\n\nWe will keep monitoring the situation.\n\nOur sincere apologies for the inconvenience.",
"created_at": "2026-06-23T10:47:55Z",
"display_at": "2026-06-23T10:47:55Z",
"id": "01KVT1G16RYQ2180V66GEYMEDS",
"incident_id": "01KVSH3YBGW1G7CCETXV2RAJT5",
"status": "identified",
"updated_at": "2026-06-23T10:47:55Z"
},
{
"body": "We are still actively working on this issue. An update from Spamhaus was received ~20 minutes ago and delisting is being propagated worldwide.\n\nWe will keep monitoring the situation.\n\nOur sincere apologies for the inconvenience.",
"created_at": "2026-06-23T08:41:25Z",
"display_at": "2026-06-23T08:41:25Z",
"id": "01KVST8D2PGWCX1KK6GR8QGVWW",
"incident_id": "01KVSH3YBGW1G7CCETXV2RAJT5",
"status": "identified",
"updated_at": "2026-06-23T08:41:25Z"
},
{
"body": "We’ve identified that three of our outbound transactional IP addresses have been blocklisted, affecting email delivery for some customers. The team is currently investigating the cause and working on delisting the IP. In the meantime, the IP address has been suspended and will not be used until the issue is resolved. This does not affect other IPs in the pool nor broadcast routes.\n\nIf you have seen a hard bounce because of this, you can safely reactivate the recipient from your suppression management.\n\n ",
"created_at": "2026-06-23T06:01:42Z",
"display_at": "2026-06-23T06:01:42Z",
"id": "01KVSH3YBG2BZ7GEGWQ26B5ZEE",
"incident_id": "01KVSH3YBGW1G7CCETXV2RAJT5",
"status": "identified",
"updated_at": "2026-06-23T06:01:42Z"
}
],
"name": "[Blocklist] Transactional IP listed in Spamhaus",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-06-23T16:24:12Z",
"status": "resolved",
"updated_at": "2026-06-23T18:20:35Z"
},
{
"created_at": "2026-06-22T12:32:08Z",
"id": "01KVQN24QMG2MXFMK97KFRJXVE",
"impact": "minor",
"incident_updates": [
{
"body": "We have not seen any new bounces due to the listing and are actively looking into resending all bounced messages.\n\nRecipients that bounced due to the Spamhaus listing should not be suppressed. If it still did so, feel free to remove these from the suppression list.\n\nOur sincere apologies for the inconvenience. ",
"created_at": "2026-06-22T13:07:29Z",
"display_at": "2026-06-22T13:07:29Z",
"id": "01KVQQ2WD33WJPEN4E439Q0ZTP",
"incident_id": "01KVQN24QMG2MXFMK97KFRJXVE",
"status": "resolved",
"updated_at": "2026-06-22T13:07:29Z"
},
{
"body": "We’ve identified that one of our outbound transactional IP addresses has been blocklisted, affecting email delivery for some customers. The team is currently investigating the cause and working on delisting the IP. In the meantime, the IP address has been suspended and will not be used until the issue is resolved. This does not affect other IPs in the pool nor broadcast routes. \n\nIf you have seen a hard bounce because of this you can safely reactivate the recipient from your suppression management.\n\nAs of 11.44 UTC, the listing has been removed and we are monitoring the situation.",
"created_at": "2026-06-22T12:32:08Z",
"display_at": "2026-06-22T12:32:08Z",
"id": "01KVQN24QM51DMB13CWB56Y40C",
"incident_id": "01KVQN24QMG2MXFMK97KFRJXVE",
"status": "monitoring",
"updated_at": "2026-06-22T12:32:08Z"
}
],
"name": "[Blocklist] Transactional IP is listed in Spamhaus",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-06-22T13:07:29Z",
"status": "resolved",
"updated_at": "2026-06-22T13:07:29Z"
},
{
"created_at": "2026-06-19T12:48:44Z",
"id": "01KVFYTCPW4SJJPTCXNN4RF6AZ",
"impact": "minor",
"incident_updates": [
{
"body": "We are not seeing any more deferrals with Outlook OLC and mark this incident as resolved.\n\nDuring the incident we have adjusted our traffic shaping to improve mitigation for incidents like this in the future. We have since seen improvements.\n\nOur sincere apologies for the inconvenience and the delay in delivery of emails sent to consumer Outlook addresses.",
"created_at": "2026-06-20T10:42:27Z",
"display_at": "2026-06-20T10:42:27Z",
"id": "01KVJ9ZVNKWDSZR68CZABB8RKH",
"incident_id": "01KVFYTCPW4SJJPTCXNN4RF6AZ",
"status": "resolved",
"updated_at": "2026-06-20T10:42:27Z"
},
{
"body": "We are seeing improvements and emails are being delivered.\n\nWe will keep monitoring the situation closely.",
"created_at": "2026-06-20T08:41:13Z",
"display_at": "2026-06-20T08:41:13Z",
"id": "01KVJ31W8QGJ7EE9GAT22ZYQJQ",
"incident_id": "01KVFYTCPW4SJJPTCXNN4RF6AZ",
"status": "monitoring",
"updated_at": "2026-06-20T08:41:13Z"
},
{
"body": "We are still actively remediating the issue and have changed our mitigation. You might see deferrals in your webhooks or UI instead of delayed processing. Please note emails are still being retried.\n\nTo make sure emails will be delivered, we have increased our maximum wait time to 24 hours instead of 12 hours and are actively monitoring the situation in case further extension is needed. We hope to hear back from Microsoft's Sender Support as soon as possible.\n\nThis issue does not impact Microsoft 365 (Outlook 365) addresses nor other providers.\n\nBroadcast is also not affected by the issue.\n\nOur sincere apologies for the inconvenience.",
"created_at": "2026-06-20T04:59:56Z",
"display_at": "2026-06-20T04:59:56Z",
"id": "01KVHPCPMT3PNGW036ZB8RFDSP",
"incident_id": "01KVFYTCPW4SJJPTCXNN4RF6AZ",
"status": "identified",
"updated_at": "2026-06-20T04:59:56Z"
},
{
"body": "We are still actively remediating the issue and have changed our mitigation. You might see deferrals in your webhooks or UI instead of delayed processing. Please note emails are still being retried.\n\nTo make sure emails will be delivered, we have increased our maximum wait time to 24 hours instead of 12 hours and are actively monitoring the situation in case further extension is needed. We hope to hear back from Microsoft's Sender Support as soon as possible.\n\nThis issue does not impact Microsoft 365 (Outlook 365) addresses nor other providers.\n\nBroadcast is also not affected by the issue.\n\nOur sincere apologies for the inconvenience.",
"created_at": "2026-06-19T21:49:59Z",
"display_at": "2026-06-19T21:49:59Z",
"id": "01KVGXSDZ0SVADADHN3FRWXX17",
"incident_id": "01KVFYTCPW4SJJPTCXNN4RF6AZ",
"status": "identified",
"updated_at": "2026-06-19T21:49:59Z"
},
{
"body": "We are still actively remediating the issue.\n\nOur automated traffic shaping has partially mitigated the issue but are awaiting further mitigation from Microsoft. Emails to Outlook OLC are still delayed and might show as Processed for an extended period of time in the UI.\n\nThis issue does not impact Microsoft 365 (Outlook 365) addresses nor other providers.\n\nBroadcast is also not affected by the issue.\n\nOur sincere apologies for the inconvenience. ",
"created_at": "2026-06-19T19:26:40Z",
"display_at": "2026-06-19T19:26:40Z",
"id": "01KVGNK0EK4PYVH1RVDZRE5Y6Z",
"incident_id": "01KVFYTCPW4SJJPTCXNN4RF6AZ",
"status": "identified",
"updated_at": "2026-06-19T19:26:40Z"
},
{
"body": "We are still actively remediating the issue.\n\nOur automated traffic shaping has partially mitigated the issue but are awaiting further mitigation from Microsoft. Emails to Outlook OLC are still delayed and might show as Processed for an extended period of time in the UI.\n\nThis issue does not impact Microsoft 365 (Outlook 365) addresses nor other providers.",
"created_at": "2026-06-19T16:20:42Z",
"display_at": "2026-06-19T16:20:42Z",
"id": "01KVGAYGJKJZ5Q40CP1YRAPBJT",
"incident_id": "01KVFYTCPW4SJJPTCXNN4RF6AZ",
"status": "identified",
"updated_at": "2026-06-19T19:26:48Z"
},
{
"body": "Our automated traffic shaping has partially mitigated the issue but are awaiting further mitigation from Microsoft. Emails to Outltook OLC are still delayed and might show as Processed for an extended period of time in the UI.\n\nThis issue does not impact Microsoft 365 (Outlook 365) addresses nor other providers.",
"created_at": "2026-06-19T13:55:48Z",
"display_at": "2026-06-19T13:55:48Z",
"id": "01KVG2N69K0PVPGQJ9GWXZF29A",
"incident_id": "01KVFYTCPW4SJJPTCXNN4RF6AZ",
"status": "identified",
"updated_at": "2026-06-19T13:55:48Z"
},
{
"body": "We have identified an issue with messages being rate limited against Outlook OLC and are actively remediating. Emails will be delivered after retries and does not impact other providers nor Microsoft 365 (Office 365) tenants.",
"created_at": "2026-06-19T12:48:44Z",
"display_at": "2026-06-19T12:48:44Z",
"id": "01KVFYTCPWQH9S2YTB23EVE9RQ",
"incident_id": "01KVFYTCPW4SJJPTCXNN4RF6AZ",
"status": "identified",
"updated_at": "2026-06-19T12:57:08Z"
}
],
"name": "Delayed sending to Outlook OLC",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-06-20T10:42:27Z",
"status": "resolved",
"updated_at": "2026-06-20T10:42:27Z"
},
{
"created_at": "2026-06-17T17:48:45Z",
"id": "01KVBB69W0HGJ17F9BFTAVAZ4Z",
"impact": "critical",
"incident_updates": [
{
"body": "We have continued monitoring and have not observed any further recurrence of this issue.\n\nThe incident is now resolved. We have completed a post-mortem and will publish it shortly with more detail on the impact, root cause, and follow-up actions.",
"created_at": "2026-06-17T20:18:44Z",
"display_at": "2026-06-17T20:18:44Z",
"id": "01KVBKRXFGDK6J7CX44698GJFY",
"incident_id": "01KVBB69W0HGJ17F9BFTAVAZ4Z",
"status": "resolved",
"updated_at": "2026-06-17T20:18:44Z"
},
{
"body": "We are seeing improvements and services are back to normal. In the meantime, we will keep monitoring the situation closely and apologies for the inconvenience this has caused.\n\n \n\nA public post-mortem will also be shared.",
"created_at": "2026-06-17T18:09:15Z",
"display_at": "2026-06-17T18:09:15Z",
"id": "01KVBCBV107HRWH3EJA3TNCX1J",
"incident_id": "01KVBB69W0HGJ17F9BFTAVAZ4Z",
"status": "monitoring",
"updated_at": "2026-06-17T18:09:15Z"
},
{
"body": "A fix is being deployed and we'll be monitoring the situation.",
"created_at": "2026-06-17T18:06:03Z",
"display_at": "2026-06-17T18:06:03Z",
"id": "01KVBC5YQBSP7RJE5CFNXJWPFC",
"incident_id": "01KVBB69W0HGJ17F9BFTAVAZ4Z",
"status": "monitoring",
"updated_at": "2026-06-17T18:06:03Z"
},
{
"body": "We have identified the issue and our team is working on a fix. We'll keep you posted.\n\nApologies for the inconvenience.",
"created_at": "2026-06-17T17:52:46Z",
"display_at": "2026-06-17T17:52:46Z",
"id": "01KVBBDNB0AGCN0T5NPZ4D4DB6",
"incident_id": "01KVBB69W0HGJ17F9BFTAVAZ4Z",
"status": "identified",
"updated_at": "2026-06-17T17:52:46Z"
},
{
"body": "We are currently investigating reports of email submitted via the SMTP relay not being processed.",
"created_at": "2026-06-17T17:48:45Z",
"display_at": "2026-06-17T17:00:00Z",
"id": "01KVBB69W0NS8P1X69ZWETKJ3Z",
"incident_id": "01KVBB69W0HGJ17F9BFTAVAZ4Z",
"status": "investigating",
"updated_at": "2026-06-17T17:52:58Z"
}
],
"name": "Email submissions not being processed",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-06-17T20:18:44Z",
"status": "resolved",
"updated_at": "2026-06-17T20:31:12Z"
},
{
"created_at": "2026-05-29T10:59:44Z",
"id": "01KSSP7PGC99T86BQ92SBWX74M",
"impact": "minor",
"incident_updates": [
{
"body": "We have not seen any regressions related to emails being queued for longer than expected. Therefore we're marking this incident as resolved.\n\nIf you still notice any issues, do reach out to support.",
"created_at": "2026-05-29T13:20:36Z",
"display_at": "2026-05-29T13:20:36Z",
"id": "01KSSY9MF5R6YGKZAST7BNED5K",
"incident_id": "01KSSP7PGC99T86BQ92SBWX74M",
"status": "resolved",
"updated_at": "2026-05-29T13:20:36Z"
},
{
"body": "A fix has been implemented and we're monitoring the situation. Queues are being processed quickly again and the time-to-inbox dropped to sub-10 seconds as expected.\n\nApologies for the inconvenience this caused.",
"created_at": "2026-05-29T12:00:18Z",
"display_at": "2026-05-29T12:00:18Z",
"id": "01KSSSPKWD8KR4JG9JVFFB8FV0",
"incident_id": "01KSSP7PGC99T86BQ92SBWX74M",
"status": "monitoring",
"updated_at": "2026-05-29T12:00:18Z"
},
{
"body": "We have identified the issue causing a delay in processing of emails and are working on a fix. Currently emails are in queue for an average of ~22 seconds, higher than the usual average of a couple milliseconds.\n\nWe will keep you posted once a fix has been implemented.",
"created_at": "2026-05-29T11:09:13Z",
"display_at": "2026-05-29T11:09:13Z",
"id": "01KSSPS2F9VQQY620AD913363D",
"incident_id": "01KSSP7PGC99T86BQ92SBWX74M",
"status": "identified",
"updated_at": "2026-05-29T11:09:13Z"
},
{
"body": "We are currently investigating a sudden increase in queue times for emails. Emails are delayed for ~2 minutes on average.\n\nWe will keep you posted.",
"created_at": "2026-05-29T10:59:44Z",
"display_at": "2026-05-29T10:59:44Z",
"id": "01KSSP7PGCNDNPSJJQP9QH03AT",
"incident_id": "01KSSP7PGC99T86BQ92SBWX74M",
"status": "investigating",
"updated_at": "2026-05-29T10:59:44Z"
}
],
"name": "Delay in sending emails",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-05-29T13:20:36Z",
"status": "resolved",
"updated_at": "2026-05-29T13:20:36Z"
},
{
"created_at": "2026-04-07T18:43:00Z",
"id": "01KNMM2KDHF9YFCCRTNZEQJSQS",
"impact": "minor",
"incident_updates": [
{
"body": "We are no longer seeing any connection issues. A post-mortem will be shared as soon as possible.\n\nOur findings have been shared with the developer of the package and will cooperate to fix the issue for the ecosystem.",
"created_at": "2026-04-07T20:31:15Z",
"display_at": "2026-04-07T20:31:15Z",
"id": "01KNMT8T37H37608RHNVB4ZR0P",
"incident_id": "01KNMM2KDHF9YFCCRTNZEQJSQS",
"status": "resolved",
"updated_at": "2026-04-07T20:31:15Z"
},
{
"body": "Fix has been deployed for the intermittent connection errors affecting SMTP submissions with larger attachments. We are now observing traffic to confirm the issue is fully resolved. No action is required from customers.",
"created_at": "2026-04-07T19:52:09Z",
"display_at": "2026-04-07T19:52:09Z",
"id": "01KNMR16TMV97CQ0T3BC15Z5NC",
"incident_id": "01KNMM2KDHF9YFCCRTNZEQJSQS",
"status": "monitoring",
"updated_at": "2026-04-07T19:52:09Z"
},
{
"body": "We are noticing degraded performance with sending larger attachment to our SMTP relay and are currently investigating the issue.",
"created_at": "2026-04-07T18:43:00Z",
"display_at": "2026-04-07T18:43:00Z",
"id": "01KNMM2KDHHK81V1SF733KG8QZ",
"incident_id": "01KNMM2KDHF9YFCCRTNZEQJSQS",
"status": "investigating",
"updated_at": "2026-04-07T18:43:00Z"
}
],
"name": "Time-outs with larger emails",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-04-07T20:31:15Z",
"status": "resolved",
"updated_at": "2026-04-07T20:31:15Z"
},
{
"created_at": "2026-03-27T18:24:35Z",
"id": "01KMR8MZKS9GFA94WEJFP5S2NJ",
"impact": "major",
"incident_updates": [
{
"body": "This incident is resolved. Our email sending API is fully operational and we are no longer seeing any errors or alerts. ",
"created_at": "2026-03-27T18:53:26Z",
"display_at": "2026-03-27T18:53:26Z",
"id": "01KMRA9S8HA2MAHQ2VXJXMVZT4",
"incident_id": "01KMR8MZKS9GFA94WEJFP5S2NJ",
"status": "resolved",
"updated_at": "2026-03-27T18:53:26Z"
},
{
"body": "We have deployed a fix for the issues with our email sending API. We are no longer seeing errors and will continue to monitor.",
"created_at": "2026-03-27T18:32:49Z",
"display_at": "2026-03-27T18:32:49Z",
"id": "01KMR941ZHGPMQ3AQXPHS3DMWP",
"incident_id": "01KMR8MZKS9GFA94WEJFP5S2NJ",
"status": "monitoring",
"updated_at": "2026-03-27T18:32:49Z"
},
{
"body": "We have identified the issue with our email sending API and are working on a fix. SMTP is not affected. We will provide updates as soon as we have more information.",
"created_at": "2026-03-27T18:24:35Z",
"display_at": "2026-03-27T18:24:35Z",
"id": "01KMR8MZKS73S153HBDV23Y51F",
"incident_id": "01KMR8MZKS9GFA94WEJFP5S2NJ",
"status": "identified",
"updated_at": "2026-03-27T18:24:35Z"
}
],
"name": "Email sending API degraded",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-03-27T18:53:26Z",
"status": "resolved",
"updated_at": "2026-03-27T18:53:26Z"
},
{
"created_at": "2026-03-25T07:36:29Z",
"id": "01KMHYRT6DKPJ0M72S9VM78FDF",
"impact": "minor",
"incident_updates": [
{
"body": "We are no longer seeing any issues and are marking this incident as resolved.\n\nWe apologise for the inconvenience this may have caused.",
"created_at": "2026-03-25T08:56:27Z",
"display_at": "2026-03-25T08:56:27Z",
"id": "01KMJ3B7RMJMHNG67JCNAAE4P2",
"incident_id": "01KMHYRT6DKPJ0M72S9VM78FDF",
"status": "resolved",
"updated_at": "2026-03-25T08:56:27Z"
},
{
"body": "The root cause has been identified and a fix has been implemented.\n\nWe will keep monitoring the results, all emails are now being forced to retry immediately.",
"created_at": "2026-03-25T08:28:08Z",
"display_at": "2026-03-25T08:28:08Z",
"id": "01KMJ1QCTT3TQE0KKFX2T0TWD9",
"incident_id": "01KMHYRT6DKPJ0M72S9VM78FDF",
"status": "monitoring",
"updated_at": "2026-03-25T08:28:08Z"
},
{
"body": "We are observing an increased amount of softbounces due to issues related to networking and are currently investigating.\n\nOnly a small percentage of traffic is impacted and will be retried in minutes.",
"created_at": "2026-03-25T07:36:29Z",
"display_at": "2026-03-25T07:36:29Z",
"id": "01KMHYRT6DJTE50S6AF5C77V28",
"incident_id": "01KMHYRT6DKPJ0M72S9VM78FDF",
"status": "investigating",
"updated_at": "2026-03-25T07:36:29Z"
}
],
"name": "Intermittent delay in delivery",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-03-25T08:56:27Z",
"status": "resolved",
"updated_at": "2026-03-25T08:56:27Z"
},
{
"created_at": "2026-03-05T09:26:47Z",
"id": "01KJYN4DGJMNZY9EPMR631NWHJ",
"impact": "major",
"incident_updates": [
{
"body": "No more regressions have been noticed and all services are still healthy.\n\nIncident has been resolved.\n\nA follow-up from our cloud provider is still expected and we are taking measures to prevent issues like this in the long-term.",
"created_at": "2026-03-05T11:11:58Z",
"display_at": "2026-03-05T11:11:58Z",
"id": "01KJYV50X870DFMTQVB4TPJPAP",
"incident_id": "01KJYN4DGJMNZY9EPMR631NWHJ",
"status": "resolved",
"updated_at": "2026-03-05T11:11:58Z"
},
{
"body": "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.\n\nAll services are healthy again and we will keep monitoring the situation.",
"created_at": "2026-03-05T10:22:12Z",
"display_at": "2026-03-05T10:22:12Z",
"id": "01KJYR9WJXQPASEGDKCXY93817",
"incident_id": "01KJYN4DGJMNZY9EPMR631NWHJ",
"status": "monitoring",
"updated_at": "2026-03-05T10:22:12Z"
},
{
"body": "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.\n\nOur team is in contact with our cloud provider to receive updates on the resolution. We will provide updates as the situation develops.",
"created_at": "2026-03-05T10:07:58Z",
"display_at": "2026-03-05T10:07:58Z",
"id": "01KJYQFTJ6YBB5DH7XC3S81YDV",
"incident_id": "01KJYN4DGJMNZY9EPMR631NWHJ",
"status": "identified",
"updated_at": "2026-03-05T10:07:58Z"
},
{
"body": "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.\n\nWrite operations and cache services were unaffected throughout.\n\nAll services have fully recovered.",
"created_at": "2026-03-05T09:40:33Z",
"display_at": "2026-03-05T09:40:33Z",
"id": "01KJYNXKRGA99KYAXNREHJMA28",
"incident_id": "01KJYN4DGJMNZY9EPMR631NWHJ",
"status": "monitoring",
"updated_at": "2026-03-05T09:40:33Z"
},
{
"body": "We are investigating possible issues related to accessing Lettermint services.\nUpdates will be shared as soon as we know more.",
"created_at": "2026-03-05T09:26:47Z",
"display_at": "2026-03-05T09:26:47Z",
"id": "01KJYN4DGJBY8TTXXV91MZ1VW9",
"incident_id": "01KJYN4DGJMNZY9EPMR631NWHJ",
"status": "investigating",
"updated_at": "2026-03-05T09:26:47Z"
}
],
"name": "Intermittent increased latency and error rate",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-03-05T11:11:58Z",
"status": "resolved",
"updated_at": "2026-03-11T15:30:28Z"
},
{
"created_at": "2026-02-17T15:24:29Z",
"id": "01KHP37W3W2MCMTEYKBA77H97A",
"impact": "minor",
"incident_updates": [
{
"body": "We are no longer seeing any deferrals related to these IP addresses and emails are sent out accordingly.",
"created_at": "2026-02-18T01:08:04Z",
"display_at": "2026-02-18T01:08:04Z",
"id": "01KHQ4MENSMSF22HSYQWFY6VTN",
"incident_id": "01KHP37W3W2MCMTEYKBA77H97A",
"status": "resolved",
"updated_at": "2026-02-18T01:08:04Z"
},
{
"body": "We're no longer seeing any bounces, but we'll keep monitoring it.",
"created_at": "2026-02-17T16:26:07Z",
"display_at": "2026-02-17T16:26:07Z",
"id": "01KHP6RQY4KA7FQWQES8D3T783",
"incident_id": "01KHP37W3W2MCMTEYKBA77H97A",
"status": "monitoring",
"updated_at": "2026-02-17T16:26:07Z"
},
{
"body": "We've identified that two of our outbound broadcast IP addresses have been ratelimited, affecting email delivery for some customers. \n\nThe team is currently investigating the cause and working on delisting the IPs. In the meantime, the IP addresses has been suspended and will not be used until the issue is resolved. This does not affect other IPs in the pool nor transactional routes. \n\nThese rate limits cause soft-bounces. We will keep retrying to send the emails.",
"created_at": "2026-02-17T15:24:29Z",
"display_at": "2026-02-17T15:24:29Z",
"id": "01KHP37W3WVKYWBGW96XJBN5XV",
"incident_id": "01KHP37W3W2MCMTEYKBA77H97A",
"status": "identified",
"updated_at": "2026-02-17T15:24:29Z"
}
],
"name": "[Ratelimit] Broadcast IP is rate-limited with Outlook (OLC)",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-02-18T01:08:04Z",
"status": "resolved",
"updated_at": "2026-03-11T15:30:28Z"
},
{
"created_at": "2026-02-13T15:20:48Z",
"id": "01KHBSE851M44V2HNFWH2DSV3G",
"impact": "none",
"incident_updates": [
{
"body": "We see improvements and no more bounces related to the block.\n\nAfter further investigation, iCloud was having issues where it was incorrectly rejecting mail with IP block responses while it was not the case. This has been confirmed with others.\n\nWe will keep monitoring the situation closely.",
"created_at": "2026-02-13T17:27:05Z",
"display_at": "2026-02-13T17:27:05Z",
"id": "01KHC0NFRRYQSRDX1THB4WV7T2",
"incident_id": "01KHBSE851M44V2HNFWH2DSV3G",
"status": "resolved",
"updated_at": "2026-02-13T18:52:16Z"
},
{
"body": "We've been notified of intermittent delivery failures due to hard bounces to iCloud, affecting email delivery for some customers. The team is currently investigating the cause and working on resolving this issue.\n\nIf you have seen a hard bounce because of this you can safely reactivate the recipient from your suppression management.",
"created_at": "2026-02-13T15:20:48Z",
"display_at": "2026-02-13T15:20:48Z",
"id": "01KHBSE851GDFK8JP9EBDZYC24",
"incident_id": "01KHBSE851M44V2HNFWH2DSV3G",
"status": "investigating",
"updated_at": "2026-02-13T15:20:48Z"
}
],
"name": "[Blocklist] Intermittent mailblocks to iCloud addresses",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-02-13T17:27:05Z",
"status": "resolved",
"updated_at": "2026-03-11T15:30:28Z"
},
{
"created_at": "2026-02-05T11:47:45Z",
"id": "01KGPT2DCVHH60JP52TQTQR663",
"impact": "major",
"incident_updates": [
{
"body": "We have confirmed everything is stable again and are working with our upstream provider to work out the final details.\n\nAs part of our post-incident process we are working on resolving any individual issues that might still have occurred. Do reach out to support if you have any questions.\n\nOur sincere apologies for the inconvenience. A post-mortem will be shared as soon as possible.",
"created_at": "2026-02-05T13:48:06Z",
"display_at": "2026-02-05T13:48:06Z",
"id": "01KGQ0YRZCD9XHE16V3TTENRYC",
"incident_id": "01KGPT2DCVHH60JP52TQTQR663",
"status": "resolved",
"updated_at": "2026-02-05T13:48:06Z"
},
{
"body": "Our services have been restored and we are no longer seeing any issues. We are closely monitoring our infrastructure to ensure everything remains stable.\n\nOnce this incident is fully resolved, we will publish a post-mortem with a detailed overview of what happened and what steps we are taking to prevent this in the future.",
"created_at": "2026-02-05T13:04:22Z",
"display_at": "2026-02-05T12:53:00Z",
"id": "01KGPYEP393HS4ZFY0WN3Y616C",
"incident_id": "01KGPT2DCVHH60JP52TQTQR663",
"status": "monitoring",
"updated_at": "2026-02-05T13:13:26Z"
},
{
"body": "At approximately 12:20 PM (CET), we started receiving reports of infrastructure issues affecting our services. This is currently causing database connectivity problems, which may result in failed API requests or delays in email processing.\n\nOur team is actively investigating the issue. We will provide updates as soon as more information is available.",
"created_at": "2026-02-05T11:47:45Z",
"display_at": "2026-02-05T11:20:00Z",
"id": "01KGPT2DCV1JSF1NQ7XSJA4GXS",
"incident_id": "01KGPT2DCVHH60JP52TQTQR663",
"status": "identified",
"updated_at": "2026-02-05T13:10:08Z"
}
],
"name": "Service Disruption",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-02-05T13:48:06Z",
"status": "resolved",
"updated_at": "2026-03-11T15:30:28Z"
},
{
"created_at": "2026-01-22T11:31:28Z",
"id": "01KFJQJH4VRDTBD4AEFEMS8VBW",
"impact": "major",
"incident_updates": [
{
"body": "The issue has been resolved and all queued emails are sent out. \n\nWe sincerely apologies for the inconvenience and will provide a write-up later today.\n\nIf you still notice any issues, do not hesitate to contact us.",
"created_at": "2026-01-22T11:49:49Z",
"display_at": "2026-01-22T11:49:49Z",
"id": "01KFJRM3ZMNZ5QZBTGMDXKW525",
"incident_id": "01KFJQJH4VRDTBD4AEFEMS8VBW",
"status": "resolved",
"updated_at": "2026-01-22T11:49:49Z"
},
{
"body": "The root cause of the issue has been identified and a fix is being rolled out.",
"created_at": "2026-01-22T11:35:18Z",
"display_at": "2026-01-22T11:35:18Z",
"id": "01KFJQSHK0TVBJT5G6MM8ADR5A",
"incident_id": "01KFJQJH4VRDTBD4AEFEMS8VBW",
"status": "identified",
"updated_at": "2026-01-22T11:35:18Z"
},
{
"body": "We are seeing issues with emails being stuck in the queue and are currently investigating this incident.",
"created_at": "2026-01-22T11:31:28Z",
"display_at": "2026-01-22T11:31:28Z",
"id": "01KFJQJH4V679C0FRYJA946XAA",
"incident_id": "01KFJQJH4VRDTBD4AEFEMS8VBW",
"status": "investigating",
"updated_at": "2026-01-22T11:31:28Z"
}
],
"name": "Delayed sending of emails",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-01-22T11:49:49Z",
"status": "resolved",
"updated_at": "2026-03-11T15:30:28Z"
},
{
"created_at": "2026-01-21T11:13:38Z",
"id": "01KFG455GHHQCFNSS5KKTNNGNB",
"impact": "minor",
"incident_updates": [
{
"body": "We are no longer seeing any deferrals related to these IP addresses and emails are sent out accordingly.",
"created_at": "2026-01-21T15:15:49Z",
"display_at": "2026-01-21T15:15:49Z",
"id": "01KFGJ0KSKR6EVA18RZ4RD31J1",
"incident_id": "01KFG455GHHQCFNSS5KKTNNGNB",
"status": "resolved",
"updated_at": "2026-01-21T15:15:49Z"
},
{
"body": "We have received an update that the sending IPs previously ratelimited have been granted better accomodation. We will keep monitoring the situation and will resume sending via these IPs automatically when we see improvements.\n\nEmails currently delayed will be retried automatically.",
"created_at": "2026-01-21T11:14:42Z",
"display_at": "2026-01-21T11:14:42Z",
"id": "01KFG473HMG98VCZ9JWZ7DR7NV",
"incident_id": "01KFG455GHHQCFNSS5KKTNNGNB",
"status": "monitoring",
"updated_at": "2026-01-21T11:14:42Z"
},
{
"body": "We've identified that two of our outbound broadcast IP addresses have been ratelimited, affecting email delivery for some customers. \n\nThe team is currently investigating the cause and working on delisting the IPs. In the meantime, the IP addresses has been suspended and will not be used until the issue is resolved. This does not affect other IPs in the pool nor transactional routes. \n\nThese rate limits cause soft-bounces. We will keep retrying to send the emails.",
"created_at": "2026-01-21T11:13:38Z",
"display_at": "2026-01-21T11:13:38Z",
"id": "01KFG455GHPFA1G3M6ZZF6N1EM",
"incident_id": "01KFG455GHHQCFNSS5KKTNNGNB",
"status": "identified",
"updated_at": "2026-01-21T11:13:38Z"
}
],
"name": "[Ratelimit] Broadcast IP is rate-limited with Outlook (OLC)",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-01-21T15:15:49Z",
"status": "resolved",
"updated_at": "2026-03-11T15:30:28Z"
},
{
"created_at": "2026-01-05T15:33:08Z",
"id": "01KE7CMTB9H6PAWPGVSD53CQKH",
"impact": "minor",
"incident_updates": [
{
"body": "All queued emails have been processed and delivery is back to normal. \n\nWe are implementing additional failover mechanisms to mitigate future upstream incidents. \n\nIf you experience further issues, please contact support.",
"created_at": "2026-01-05T16:37:29Z",
"display_at": "2026-01-05T16:37:29Z",
"id": "01KE7GAN6PRH3B43AH57CK1NY9",
"incident_id": "01KE7CMTB9H6PAWPGVSD53CQKH",
"status": "resolved",
"updated_at": "2026-01-05T16:37:29Z"
},
{
"body": "We are seeing improvements and the issue is marked as resolved with our cloud provider. \n\nCurrently, the backlog of queued emails is being processed and everything should be sent out as soon as possible. ",
"created_at": "2026-01-05T16:33:25Z",
"display_at": "2026-01-05T16:33:25Z",
"id": "01KE7G3658KN0WDQCYKA9N7P2N",
"incident_id": "01KE7CMTB9H6PAWPGVSD53CQKH",
"status": "monitoring",
"updated_at": "2026-01-05T16:33:25Z"
},
{
"body": "The incident at our cloud provider is still ongoing.\n\n \n\nIn the meantime, we are working hard on mitigating impact and will keep you posted. Emails that are marked as queued will be sent out as soon as possible and we want to reassure you that no data is lost.",
"created_at": "2026-01-05T16:13:42Z",
"display_at": "2026-01-05T16:13:42Z",
"id": "01KE7EZ3N0Z497V62WXJ3YBKYH",
"incident_id": "01KE7CMTB9H6PAWPGVSD53CQKH",
"status": "identified",
"updated_at": "2026-01-05T16:13:42Z"
},
{
"body": "We have identified an issue with our upstream provider causing time-outs when writing mails to storage, causing delays in sending.\n\nWe will keep you updated while we are working on resolving this incident.",
"created_at": "2026-01-05T15:33:08Z",
"display_at": "2026-01-05T15:33:08Z",
"id": "01KE7CMTB9PYM0RF3C4N9EHQKD",
"incident_id": "01KE7CMTB9H6PAWPGVSD53CQKH",
"status": "identified",
"updated_at": "2026-01-05T15:33:08Z"
}
],
"name": "Intermittent delayed sending of emails",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2026-01-05T16:37:29Z",
"status": "resolved",
"updated_at": "2026-03-11T15:30:28Z"
},
{
"created_at": "2025-12-12T21:55:53Z",
"id": "01KCA90DFJ6280G6WACKZMPAZ8",
"impact": "critical",
"incident_updates": [
{
"body": "During our scheduled maintenance window, we experienced a temporary disruption in service availability. This resulted in database connectivity errors for some of our services.\n\nThe disruption was caused by an unexpected behavior change in our database connection pooling layer after a routine component update. The update enforced stricter SSL parameter negotiation than previous versions, which prevented the pooler from establishing secure connections to the backend database.\n\nThis was an undocumented upstream edge case and was not caught by our pre-deployment testing.\n\nWe detected the issue quickly and reverted the update, after which connectivity was restored. We are tracking the upstream fix and will roll it out only after additional validation.\n\nImpact was limited because maintenance is performed during low-traffic windows, but we apologize for the disruption.\n\nTo reduce the likelihood of similar incidents, we are:\n\n• Further aligning staging and production configuration for database connectivity and SSL behavior.\n\n• Strengthening our maintenance readiness checks, including reviewing relevant upstream issues and release notes before changes are applied.\n\nAs always, we are committed to improving reliability and continuously refining our processes.",
"created_at": "2025-12-12T21:55:54Z",
"display_at": "2025-12-12T21:16:00Z",
"id": "01KCA90DFJ99TEAGYFQHWB22MT",
"incident_id": "01KCA90DFJ6280G6WACKZMPAZ8",
"status": "resolved",
"updated_at": "2025-12-12T21:55:54Z"
},
{
"body": "An incident occurred during routine maintenance.",
"created_at": "2025-12-12T21:55:53Z",
"display_at": "2025-12-12T21:10:00Z",
"id": "01KCA90DFJP10BGBR06YFS476Q",
"incident_id": "01KCA90DFJ6280G6WACKZMPAZ8",
"status": "identified",
"updated_at": "2025-12-12T21:55:53Z"
}
],
"name": "Database Connectivity Interruption",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2025-12-12T21:16:00Z",
"status": "resolved",
"updated_at": "2026-03-11T15:30:28Z"
},
{
"created_at": "2025-12-10T11:06:29Z",
"id": "01KC3Z1WFGD4G4QVX8P5JZN35S",
"impact": "major",
"incident_updates": [
{
"body": "All emails have been sent out successfully again and are no longer seeing any issues.\n\nWe are going to work on improving resilience against upstream provider issues related to object storage and will share updates on this in the future.",
"created_at": "2025-12-10T12:19:10Z",
"display_at": "2025-12-10T12:19:10Z",
"id": "01KC436YTQDKG1QH846N7CKNR2",
"incident_id": "01KC3Z1WFGD4G4QVX8P5JZN35S",
"status": "resolved",
"updated_at": "2025-12-10T12:19:10Z"
},
{
"body": "The incident with our upstream provider has been resolved.\n\nNewly submitted emails will be processed instantly and we are working on retrying those that are being held in queue.",
"created_at": "2025-12-10T11:46:42Z",
"display_at": "2025-12-10T11:46:42Z",
"id": "01KC41BH093HWXT38FF7VFXMPN",
"incident_id": "01KC3Z1WFGD4G4QVX8P5JZN35S",
"status": "monitoring",
"updated_at": "2025-12-10T11:46:42Z"
},
{
"body": "We have identified an issue with our upstream provider causing time-outs when writing mails to storage, causing delays in sending.\n\nWe will keep you updated while we are working on resolving this incident.",
"created_at": "2025-12-10T11:06:29Z",
"display_at": "2025-12-10T11:06:29Z",
"id": "01KC3Z1WFGCAKPFXBG78TNKBEM",
"incident_id": "01KC3Z1WFGD4G4QVX8P5JZN35S",
"status": "identified",
"updated_at": "2025-12-10T11:06:29Z"
}
],
"name": "Intermittent delayed sending of emails",
"page_id": "01JNQWB8KEXGR5AAB87T7F51FB",
"resolved_at": "2025-12-10T12:19:10Z",
"status": "resolved",
"updated_at": "2026-03-11T15:30:28Z"
}
],
"page": {
"id": "01JNQWB8KEXGR5AAB87T7F51FB",
"name": "Lettermint",
"updated_at": "2026-09-23T20:01:52Z",
"url": "https://status.lettermint.co/"
}
}