SendGrid Outage History

SendGrid's Sender Engagement Quality (SEQ) API endpoint experienced degraded performance for 1.1 hours on May 14th, 2026, starting around 9:34 AM. Users were unable to access the SEQ API endpoint even with correct permission keys, though email sending functionality remained unaffected. Engineers identified the root cause, implemented a fix, and confirmed full resolution by 10:47 AM.

SendGrid experienced 5xx errors affecting website services for 37 minutes on 05/12/2026 from 16:10 to 16:27 PDT. Users encountered issues accessing subusers, domain authentication, link branding records, account access, and account statistics, though mail sending functionality remained unaffected. Engineers implemented a fix and confirmed all services returned to normal operation.

SendGrid experienced an issue where invited teammates were unable to join their organizations and were instead prompted to create standalone Twilio Unified accounts, preventing new team members from accessing their intended organizations. The issue affected teammate invitation functionality but did not impact mail sending services. Engineers implemented a fix after 1.8 hours, requiring affected users to request new invite links and clear their browser cache and cookies before attempting to join again.

SendGrid customers experienced email delays for messages sent between 5:00pm and 5:15pm PDT, affecting the Email Activity component. Engineers identified the root cause and worked to deliver the delayed emails while ensuring new mail send requests continued processing normally. The issue was fully resolved after 6.1 hours with all services returning to normal operation.

SendGrid experienced an issue with incorrect tax amounts on customer invoices starting around 9am PST on May 5, 2026, lasting 5.8 hours. The tax calculation error affected billing but did not impact email sending functionality. Engineers implemented a fix that corrected all invoices, with automatic refunds processed for overcharged customers and updated balances applied for undercharged accounts.

SendGrid experienced a 117.5-hour incident affecting Legacy Marketing customers where contact engagement data (clicks and opens) was delayed in updating, causing issues with list segmentation and disabled campaign click data export options. The incident took several days to fully resolve, with engineers processing the backlog of delayed engagement tracking and segmentation data through May 1st before completing the fix. Mail sending functionality remained unaffected throughout the incident, and all contact engagement data and segmentation features were restored to normal operation.

SendGrid's Design Editor experienced a 28.8-hour outage where users could not move or drag-and-drop modules within email templates, affecting Marketing Campaigns and API components. The issue was traced to Chrome browser version 147, with SendGrid recommending users switch to Safari or Firefox as a workaround. Engineers resolved the underlying compatibility issue and confirmed normal operations were restored.

SendGrid experienced delays in contact uploads and deletions for TNE Marketing Campaigns starting around 04:30 PST on April 17th, 2026, lasting approximately 1.3 hours. The issue affected Marketing Campaigns functionality but did not impact mail sending capabilities, and Legacy Marketing remained unaffected. Engineers implemented a fix and confirmed full resolution by 06:13 PST, with all services returning to normal operation.

EU-located subusers were unable to send emails through SendGrid's API v3, receiving "User is not authorized to send mail based on their regional attribute" errors. The issue lasted 2.8 hours starting around 08:30 AM PST on April 15th, 2026, affecting only email sending functionality for EU subusers. Engineers implemented a fix and confirmed resolution after monitoring system performance.

Starting around 07:30 AM PST on April 15th, 2026, SendGrid customers were unable to create support tickets through the website, being redirected to a blank page instead, though chat support remained functional. The issue affected only the support ticket system on the website and did not impact mail sending services. Engineers implemented a fix and confirmed full resolution after 32 minutes of monitoring.