SendGrid Status · History · Incident #138288
RESOLVED503 Errors When Calling Comms-API
Minor · Started Sep 17, 2026 · 8:57 AM
SendGrid Status · History · Incident #138288
RESOLVEDMinor · Started Sep 17, 2026 · 8:57 AM
Duration
< 1m
Severity
Minor
Detection lead
—
User reports
—
Summary
Starting on 2026-09-16 ~19:00 UTC customers were experiencing 503 errors while calling comms-api messages endpoints. 128 requests took 1 minute and eventually got failed by the timeout. After 19:30 there were no 503 errors observed anymore but the root cause of the issue is unclear.
Started
Sep 17, 2026 · 8:57 AM
Resolved
Sep 17, 2026 · 8:57 AM
Duration
< 1m
Severity
None
Event timeline
Resolved
Sep 17 · 8:57 AM SendGridStarting on 2026-09-16 ~19:00 UTC customers were experiencing 503 errors while calling comms-api messages endpoints. 128 requests took 1 minute and eventually got failed by the timeout. After 19:30 there were no 503 errors observed anymore but the root cause of the issue is unclear.
Pattern
MMS Delivery Failures from a Subset of Twilio Short Codes to Multiple Networks in United States
Sep 17, 2026
View incident →MMS Delivery Delyas and Failures from a Subset Of Twilio Longcode to Optus Australia
Sep 17, 2026 · 4h 9m
View incident →SMS Delivery Delays from Twilio to H3G United Kingdom
Sep 17, 2026 · 6h 37m
View incident →Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.