Is Twilio down right now?

No. Our checks are finding no problems with Twilio right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Twilio continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are API errors, messages not sending, calls dropping, voice / video chat, can't connect, no response / timing out and website / app down. Those are the options the report button offers for Twilio, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Twilio specifically, Twilio hands your traffic to carriers it does not control, so problems are usually limited to one country, one carrier or one channel. SMS to a single network can fail while voice and every other destination work, which is why their incidents are listed per product and per region. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Twilio, send a test message to a number on a different carrier, ideally in another country. Delivery to one carrier and not another is routing rather than Twilio being down. The API returning errors for every request is them. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Twilio's side. Specifically: check each message's status in the console before resending. Messages normally sit queued rather than failing, so resending creates duplicates that all arrive at once when the queue drains, which is worse for your recipients than the delay was. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Twilio publishes a machine-readable status feed, so our first check reads it directly and reports what Twilio itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.twilio.com, and it is linked further up this page. That is Twilio's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Twilio or twilio.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Twilio's own support, not us.