{
  "meta": {
    "version": "v1",
    "pricing": {
      "public": {
        "label": "Public",
        "description": "Read-only API access for lightweight status checks and public integrations."
      },
      "premium": {
        "label": "Premium",
        "description": "API keys with higher hourly quotas, plus Slack, Teams, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-08-18T19:12:48.796Z"
  },
  "data": {
    "id": "incident_instatus_stytch_cmsx7bm7805qd10pi1zmp87a5",
    "slug": "stytch-emails-not-being-delivered-2026-08-17",
    "title": "Emails not being delivered",
    "summary": "We extend our sincerest apologies for this outage. On 17 August 2026, between 02:15 and 05:15 PT (09:15–12:15 UTC), all outbound email from Stytch failed, including email magic links, email OTPs, and password reset emails. Service was restored at 05:15 PT. **What happened**: This",
    "status": "resolved",
    "severity": "major",
    "startedAt": "2026-08-17T09:27:00+00:00",
    "updatedAt": "2026-08-18T00:00:00+00:00",
    "resolvedAt": "2026-08-18T00:00:00+00:00",
    "provider": {
      "slug": "stytch",
      "name": "Stytch"
    },
    "affectedServices": [
      {
        "slug": "stytch-api",
        "name": "API"
      },
      {
        "slug": "stytch-messaging",
        "name": "Message delivery"
      }
    ],
    "links": {
      "html": "/incidents/stytch-emails-not-being-delivered-2026-08-17",
      "api": "/api/v1/incidents/stytch-emails-not-being-delivered-2026-08-17",
      "providerHtml": "/providers/stytch",
      "alerts": "https://outagedeck.com/account?stack=stytch&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Stytch communicated this event on the official status page.",
    "source": {
      "id": "source_stytch_status",
      "kind": "official_api",
      "name": "Stytch Status",
      "checkedAt": "2026-08-18T19:10:19.442+00:00",
      "officialUrl": "https://status.stytch.com",
      "statusPageUrl": "https://status.stytch.com"
    },
    "updates": [
      {
        "id": "update_instatus_stytch_cmsx7bm7805qd10pi1zmp87a5_20260817t092700000z",
        "status": "investigating",
        "body": "We are currently investigating this incident.",
        "createdAt": "2026-08-17T09:27:00+00:00"
      },
      {
        "id": "update_instatus_stytch_cmsx7bm7805qd10pi1zmp87a5_20260817t121400000z",
        "status": "monitoring",
        "body": "We've mitigated the issue and emails are now being delivered. Currently monitoring.",
        "createdAt": "2026-08-17T12:14:00+00:00"
      },
      {
        "id": "update_instatus_stytch_cmsx7bm7805qd10pi1zmp87a5_20260817t130000000z",
        "status": "resolved",
        "body": "The incident should be resolved; we have put in mitigations and will continue to monitor. A small percentage of users may see some lingering deliverability issues as we catch up. We apologize for the inconvenience.",
        "createdAt": "2026-08-17T13:00:00+00:00"
      },
      {
        "id": "update_instatus_stytch_cmsx7bm7805qd10pi1zmp87a5_20260817t160000000z",
        "status": "resolved",
        "body": "An email spam attack triggered our automatic provider failover, and we experienced sending difficulties with our secondary provider, causing Stytch emails to be unable to be sent. A fix was put in place to mitigate email spam but we were unable to merge this due to an upstream [GitHub incident](https://www.githubstatus.com/incidents/zkxwbgr0cnmx), resulting in delays in mitigating the issue. We will update this postmortem with additional details as soon as possible with planned near-term mitigations to prevent this from occurring again in the future.",
        "createdAt": "2026-08-17T16:00:00+00:00"
      },
      {
        "id": "update_instatus_stytch_cmsx7bm7805qd10pi1zmp87a5_20260818t000000000z",
        "status": "resolved",
        "body": "We extend our sincerest apologies for this outage. On 17 August 2026, between 02:15 and 05:15 PT (09:15–12:15 UTC), all outbound email from Stytch failed, including email magic links, email OTPs, and password reset emails. Service was restored at 05:15 PT. **What happened**: This outage was triggered by abuse of free-tier email sending, a pattern we defend against continuously. In this case, our abuse controls did not engage in time, and a large volume of spam was sent before we intervened. That volume exhausted our sending quota with our primary email provider, which normally handles the majority of traffic. Automated failover and alerting fired, and our on-call engineer fully failed over to our secondary email provider within 20 minutes. That failover appeared to succeed: The secondary provider accepted our sends and reported them as successful 200s. However, the secondary provider was not delivering those emails due to the previous spam volume. As a result, we believed email had been restored when it had not. We received customer reports beginning at 03:15 PT and confirmed the true state of email sends at 05:01 PT. We restored service at 05:15 PT, banned the malicious accounts, and implemented new safeguards against the abuse seen. **Impact**: All email sent during the window failed permanently. Any authentication email a user requested between 02:15 and 05:15 PT never arrived, and users would need to request a new one after 05:15 PT. **Ongoing impact on deliverability**: The spam volume sent from our infrastructure has affected our sender reputation for `login@stytch.com`. For some time, a higher-than-normal share of legitimate emails may land in recipients' spam folders. We are working with our providers on reputation remediation and expect this to improve over the coming days. No action is required. If your users report missing authentication emails, please ask them to check their spam folder. **What we're changing**: We have already implemented new ",
        "createdAt": "2026-08-18T00:00:00+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}