SendGrid outage on May 3 — 18h 15m disruption
May 3, 02:03 AM → May 3, 08:19 PM · 18h 15m · medium
An incident affecting SendGrid services was detected on May 3, 2026, at 02:03 UTC. This disruption was initially identified through user reports. Services were fully restored by 20:19 UTC on the same day.
Impact
During the incident, users reported issues primarily categorized as 'Website down'. A total of 314 user reports were received over the 18-hour 15-minute period. There were no specific regional concentrations identified among the reported issues. The disruption affected users attempting to access or utilize SendGrid services.
Top reported issues
- Website down314
Incident timeline
- May 3, 02:03 AM
PulseWatch detected elevated report volume (medium severity)
- May 3, 03:45 AM
Peak of 4 reports in 15 minutes (baseline 1.3)
- May 3, 01:58 PM
Status updated: possible issue
- May 3, 02:08 PM
Status updated: possible issue
- May 3, 02:13 PM
Status updated: possible issue
- May 3, 02:23 PM
Status updated: possible issue
- May 3, 02:28 PM
Status updated: possible issue
- May 3, 02:38 PM
Status updated: possible issue
- May 3, 02:43 PM
Status updated: possible issue
- May 3, 02:53 PM
Status updated: possible issue
- May 3, 02:58 PM
Status updated: possible issue
- May 3, 03:08 PM
Status updated: possible issue
- May 3, 03:13 PM
Status updated: possible issue
- May 3, 03:23 PM
Status updated: possible issue
- May 3, 03:28 PM
Status updated: possible issue
- May 3, 03:38 PM
Status updated: possible issue
- May 3, 03:43 PM
Status updated: possible issue
- May 3, 03:53 PM
Status updated: possible issue
- May 3, 03:58 PM
Status updated: possible issue
- May 3, 04:09 PM
Status updated: possible issue
- May 3, 04:14 PM
Status updated: possible issue
- May 3, 04:28 PM
Status updated: possible issue
- May 3, 04:38 PM
Status updated: possible issue
- May 3, 04:43 PM
Status updated: possible issue
- May 3, 04:53 PM
Status updated: possible issue
- May 3, 04:58 PM
Status updated: possible issue
- May 3, 05:08 PM
Status updated: possible issue
- May 3, 05:13 PM
Status updated: possible issue
- May 3, 05:23 PM
Status updated: possible issue
- May 3, 05:28 PM
Status updated: possible issue
- May 3, 05:38 PM
Status updated: possible issue
- May 3, 05:43 PM
Status updated: possible issue
- May 3, 05:53 PM
Status updated: possible issue
- May 3, 05:58 PM
Status updated: possible issue
- May 3, 06:08 PM
Status updated: possible issue
- May 3, 06:13 PM
Status updated: possible issue
- May 3, 06:23 PM
Status updated: possible issue
- May 3, 06:28 PM
Status updated: possible issue
- May 3, 06:38 PM
Status updated: possible issue
- May 3, 06:43 PM
Status updated: possible issue
- May 3, 06:53 PM
Status updated: possible issue
- May 3, 06:58 PM
Status updated: possible issue
- May 3, 07:08 PM
Status updated: possible issue
- May 3, 07:13 PM
Status updated: possible issue
- May 3, 07:23 PM
Status updated: possible issue
- May 3, 07:28 PM
Status updated: possible issue
- May 3, 07:38 PM
Status updated: possible issue
- May 3, 07:43 PM
Status updated: possible issue
- May 3, 07:53 PM
Status updated: possible issue
- May 3, 07:58 PM
Status updated: possible issue
- May 3, 08:08 PM
Status updated: possible issue
- May 3, 08:13 PM
Status updated: possible issue
- May 3, 08:19 PM
Report volume returned to baseline — incident resolved
Official updates
- May 3, 02:03 AM
SendGrid status page acknowledged the incident.
View official source