- Level
- confirmed
- Worst impact
- Degraded
- Components
- Lookup
- Down Index
- 18of 100
What to do
Check whether you use Twilio Lookup. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 37m it lasted.
Anything that failed between 2026-04-27 23:17 UTC and 2026-04-28 00:53 UTC may need a replay.Subscribe to Twilio's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Twilio 2
- monitoring
Our engineers identified an issue where we were seeing an increased error rate for some customers using the Identity Match Lookup V2 API package, all other packages are normal. A fix has been applied and we are observing improvements. We will provide an update in 2 hours or a soon as more information becomes available.
provider
- resolved
We are no longer seeing an increased error rate for some customers using the Identity Match Lookup V2 API package, all packages are working normally. This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-850eb2b7b6
Is Twilio still down?
No, this incident was resolved 2026-04-28 00:53 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
1h 37m, from 2026-04-27 23:17 UTC to 2026-04-28 00:53 UTC, by the times Twilio posted.
What was affected?
Twilio named Lookup.
What caused it?
Twilio hasn't published a root cause. If it does, it shows here.
Where does this come from?
Twilio's official status page, https://status.twilio.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.