Twilio: Conversation Relay returns unexpected “last:false” Response
Timeline of updates
- resolved
We are no longer experiencing the Issue with conversation Relay where it returns unexpected “last:false” response. This incident has been resolved.
From Twilio’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Twilio, started 2025-04-22 09:16 UTC, resolved after 57 min, 1 update(s).
- Title
- Conversation Relay returns unexpected “last:false” Response
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/n8f4393767l1
Twilio profileRecent Twilio incidentsAll outages on April 22, 2025Twilio in April 2025MarkdownJSON