APIs: messaging, media, analytics
Degraded / minor incident SendGrid status
sendgrid.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
SendGrid's status page shows “Degraded / minor incident” in Realtime Transcriptions and Recording Transcriptions US1; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet. Amazon Web Services, a provider it may run on (inferred), also reports trouble. Coincidence, not causation.
confidence: low Vendor: minor issue · users: normal · routing: no data · upstream providers: major.
- Vendor status page Degraded / minor incident · 8 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Amazon Web Services: Major outage
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Realtime Transcriptions, Recording Transcriptions US1, Speech Recognition (Gather Speech) US1
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 19 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 15 h 18 min |
Evidence
- Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
- Vendor stage: resolved on “Speech Recognition and Real-Time Transcription Failures in US1”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- Amazon Web Services reports an issue. SendGrid may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside SendGrid's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data · upstream providers: major. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
SendGrid may run on Amazon Web Services (inferred). We don't map other services that depend on SendGrid. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on SendGrid or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with SendGrid. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Speech Recognition and Real-Time Transcription Failures in US1
minor resolved · started · resolved
4 updates
- investigating
We are investigating an issue with speech recognition and real-time transcription in US1. Users may experience failures with speech-to-text processing affecting <Gather> and real-time transcription. We will provide another update in 1 hour or as soon as more information becomes available.
- identified
We have identified the issue of speech recognition failures for Voice in US1. Customers may experience no speech result when using `<Gather input="speech">`, and real-time transcription sessions may start without the first few seconds of audio transcribed or continue with a different transcription engine. Post-call transcriptions may also complete more slowly than usual. As a workaround, customers may use an alternative speech recognition provider where configurable. We will provide another update in 1 hour or as soon as more information becomes available.
- monitoring
Our engineers have mitigated the issue and are monitoring system performance. Speech recognition and real-time transcription services in US1 are returning to normal, and transcription processing for call recordings may continue to complete more slowly while systems stabilize. We will provide another update in 2 hours or as soon as more information becomes available.
- resolved
We have monitored and resolved the issue with speech recognition and real-time transcription features in US1. All services are now operating normally at this time.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.