communications
Is Twilio down right now?
Our independent multi-region reading is: reachable.
Independently measured by StackWitness. We ping each service host ourselves (reachability) and also read its status page. The strong signal is when a host is unreachable while the vendor claims operational.
Current status
We reached the host; the vendor reports a problem. Reachability does not dispute a vendor outage report.
reachable = the service host answered our probe; not a guarantee the product is fully healthy
Incident timeline
No independently measured incidents in this window.
Probe latency (this week)
Probe round-trip time and reachability outcomes only. Not full product health or a vendor SLA.
7 disruptions · baseline ~30ms p50 · scale fits this week’s range (not a fixed 0-100ms axis)
Line / fill = successful probe p50 · Bands = disruption windows · Floor ticks = fail share in bucket
- Elevated probe latency (p50 160ms, p95 346ms vs baseline ~30ms) between 2026-10-17T04:05:12.490Z and 2026-10-17T10:05:12.490Z. Probe RTT only, not full product health.
- Elevated probe latency (p50 147ms, p95 334ms vs baseline ~30ms) between 2026-10-18T04:05:12.490Z and 2026-10-18T10:05:12.490Z. Probe RTT only, not full product health.
- Elevated probe latency (p50 127ms, p95 371ms vs baseline ~30ms) between 2026-10-19T04:05:12.490Z and 2026-10-19T10:05:12.490Z. Probe RTT only, not full product health.
- Elevated probe latency (p50 48ms, p95 383ms vs baseline ~30ms) between 2026-10-20T04:05:12.490Z and 2026-10-20T10:05:12.490Z. Probe RTT only, not full product health.
- Elevated probe latency (p50 117ms, p95 364ms vs baseline ~30ms) between 2026-10-21T04:05:12.490Z and 2026-10-21T10:05:12.490Z. Probe RTT only, not full product health.
- Elevated probe latency (p50 103ms, p95 340ms vs baseline ~30ms) between 2026-10-22T04:05:12.490Z and 2026-10-22T10:05:12.490Z. Probe RTT only, not full product health.
- Elevated probe latency (p50 70ms, p95 408ms vs baseline ~30ms) between 2026-10-23T04:05:12.490Z and 2026-10-23T10:05:12.490Z. Probe RTT only, not full product health.
How to read this page
StackWitness shows two columns for Twilio: independent multi-region reachability (our probes of the service host) and the vendor's own status page (self-report). Divergence matters most when we cannot reach a host the vendor still calls operational. Reachable means the host answered our probe; it is not a promise every feature works, and we never issue a compliance verdict.
Questions
Is Twilio down?
StackWitness independently pings the Twilio service host for reachability from multiple regions and also reads the vendor status page. Reachable means the host answered our probe; it is not a claim that every product feature is healthy. We never issue a compliance verdict.
How does StackWitness know if Twilio is down?
We ping the Twilio service host for reachability from multiple regions and read the vendor status page. The signal worth acting on is when we cannot reach a host the vendor still calls operational.
What does "reachable" mean here?
The host answered our probe from our regions. It is not a claim every Twilio feature is healthy, and we never issue a compliance verdict.
Measurement window: → .
We independently ping this service host (reachability) and also read its vendor status page. The strong signal is when we cannot reach a host that still claims to be operational. We never invent calm green or issue a compliance verdict.