Minor impactResolvedCommunication

SendGrid incident: RateQueue Host Down Did Not Recover

SendGrid reported this minor-impact incident on its official status page on Nov 3, 2026, 02:14 UTC. It was resolved after 1d 15h.

Right now SendGrid is operational. Live SendGrid status →

🔔 Get alerted when SendGrid has issuesFree · email alerts · no credit card
Nov 3, 2026, 02:14 UTC
started
Nov 4, 2026, 18:09 UTC
resolved
1d 15h
duration
Minor
impact

Affected components

  • SMS
  1. resolvedNov 4, 2026, 18:09 UTC

    We are no longer experiencing the issue causing delays in messages. This incident has been resolved.

  2. monitoringNov 4, 2026, 16:13 UTC

    Messaging is operating normally. We will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.

  3. identifiedNov 4, 2026, 03:47 UTC

    The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 16 hours or as soon as new information is available.

  4. identifiedNov 3, 2026, 19:13 UTC

    The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 8 hours or as soon as new information is available.

  5. identifiedNov 3, 2026, 10:51 UTC

    Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available.

  6. identifiedNov 3, 2026, 06:55 UTC

    Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available.

  7. identifiedNov 3, 2026, 04:53 UTC

    Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available

  8. identifiedNov 3, 2026, 02:50 UTC

    Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available

  9. investigatingNov 3, 2026, 02:14 UTC

    We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available

What APIStatus.watch saw

Our 5-minute checks didn't record a change in SendGrid's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does SendGrid have incidents?

SendGrid reported 509 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 6h 11m. See SendGrid's uptime and incident history