SendGrid's Flex Plugins CLI was degraded for 3h 19m on 29 September 2026, unable to publish plugins. The fault sat inside Twilio's (SendGrid's parent) tooling, not in your own code or deployment.
Started
13:56 UTC
Duration
Lasted 3h 19m
Source
IsDown
Next time
SendGrid is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
The incident started at 13:56 UTC when SendGrid's status page reported Flex Plugins CLI as degraded, specifically that it could not publish plugins. The first update said engineering had identified the issue and was working on a patch, with another update promised in an hour. That promise slipped: the next update, at 14:52, repeated almost the same wording but pushed the estimate out to two hours. At 16:43 the status moved to monitoring, saying the CLI was operating normally again, with a further check-in due in 30 minutes. The incident was marked resolved at 17:12, just over three hours after it began. The resolution note is specific: version 7.1.3 of Flex Plugins CLI was released with a fix, and anyone affected needed to upgrade to resume publishing. That detail matters, because it means the CLI did not simply recover on its own. If you were stuck mid-publish during the window, operating normally again did not help until you pulled the new version. No components list was published alongside this incident, so there's no record of which other SendGrid services, if any, were implicated. No user reports were filed during the window on this page. Twilio's status page is the only public record of what happened; there is no separate post-mortem.
Learning
This incident sat in a specific publishing tool, Flex Plugins CLI, rather than in SendGrid's mail sending or API layer, which is why an uptime check against the API would have stayed green the whole time. Our own probes, run against the api component from both EU and NA regions, show 100% uptime over the past 24 hours, 7 days and 30 days. That is not a contradiction: the probes watch whether the API answers, and it did, while the CLI used to publish plugins was the part that broke. This is a common shape of outage for platforms built from many discrete tools, where one piece can degrade without moving the needle on the headline service's availability. The fix here required action on your side too, upgrading to CLI version 7.1.3, which no automated monitoring would have told you to do. Watching your own endpoints only tells you your half is fine. UptimeRobot watching SendGrid's components means you can see when the fault is on their side, so you stop guessing about who broke what.
