Status
Welcome to the Twilio status page. Here you will find real-time information about status of our services.
All Systems Operational
Programmable SMS Operational
Shortcode Operational
MMS Operational
SMS Operational
Programmable Voice Operational
PSTN Operational
SIP Operational
Client Web Operational
Client Mobile ? Operational
Conference ? Operational
Recording ? Operational
Queue ? Operational
Text-to-Speech ? Operational
Transcription ? Operational
TwiML Operational
Programmable Video Operational
Rooms Operational
Network Traversal Service ? Operational
Elastic SIP Trunking ? Operational
Programmable Chat Operational
Authy Operational
Lookup ? Operational
Console Operational
Phone Numbers ? Operational
REST API ? Operational
TaskRouter ? Operational
Support Center ? Operational
Developer Center Operational
Pricing and Usage Operational
Debugger Operational
Documentation Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
API Uptime
Fetching
API Response Time - North America
Fetching
API Response Time - Europe
Fetching
Past Incidents
Feb 22, 2017

No incidents reported today.

Feb 21, 2017
Resolved - This incident has been resolved.
Feb 21, 13:52 PST
Monitoring - We are still processing messages affected by earlier issue for a small subset of accounts. There are no new delays on message logs. Next update in 2 hours.
Feb 21, 12:33 PST
Investigating - We are experiencing delays in message logs of up to 30 minutes. Inbound and outbound message delivery is not impacted.
Feb 21, 11:25 PST
Feb 20, 2017
Resolved - Inbound calls in France (+3397) are fully operational.
Feb 20, 00:01 PST
Update - We are continuing to investigate an issue impacting inbound calls in France (+3397). We are working with our carrier partners to resolve the issue and will provide the next update in 1 hour.
Feb 19, 22:16 PST
Investigating - We are currently investigating an issue impacting inbound calls in France (+3397). We are working with our carrier partners to resolve the issue and will provide the next update in 1 hour.
Feb 19, 21:11 PST
Feb 18, 2017

No incidents reported.

Feb 17, 2017

No incidents reported.

Feb 16, 2017
Resolved - All services are fully operational.
Feb 16, 18:19 PST
Monitoring - Our engineers have resolved the the unfiltered search failures in the console. We will continue to monitor. At this time, all services are fully operational.
Feb 16, 17:33 PST
Identified - Our engineers have identified the cause of the unfiltered phone number search failures in the console, and are working to deliver the fix. We will provide another update in 30 minutes.
Feb 16, 17:00 PST
Investigating - We are currently experiencing issues with unfiltered phone number searches in the console returning no results. The Phone Numbers API is not impacted. Our engineers are working on the resolution and we will provide an update as quickly as possible.
Feb 16, 16:38 PST
Resolved - Messaging is fully operational.
Feb 16, 14:15 PST
Update - Our engineers have resolved issues with scrambled message bodies for a small subset of SMS from a US carrier partner. We are continuing to monitor.
Feb 16, 13:16 PST
Monitoring - Our engineers have completed routing changes to resolve issues with scrambled message bodies for a small subset of SMS from a US carrier partner. We are monitoring to confirm services are fully operational.
Feb 16, 13:02 PST
Investigating - We observed issues with message bodies scrambled for a small subset of SMS bodies from a carrier partner. Our engineers are rerouting to restore services. Next update in 15 minutes.
Feb 16, 12:32 PST
Resolved - Phone number query capabilities in the console are confirmed fully operational.
Feb 16, 11:15 PST
Monitoring - We have resolved the issue with failing phone number searches in the console. We will continue to monitor. All systems are fully operational.
Feb 16, 10:44 PST
Investigating - We are currently experiencing issues with unfiltered phone number searches in the console returning no results. The Phone Numbers API is not impacted. Our engineers are working on the resolution and we will provide an update as quickly as possible.
Feb 16, 10:39 PST
Resolved - We have confirmed resolution for issues with scrambled SMS message bodies from our carrier partner. All services remain fully operational.
Feb 16, 11:15 PST
Monitoring - We have resolved the issue with scrambled SMS message bodies from our carrier partner. We will continue to monitor the service. All SMS services are fully operational.
Feb 16, 10:38 PST
Investigating - We are investigating intermittent issues with SMS message delivery in US. Message bodies can be scrambled or formatted incorrectly. Primary carrier affected in US is Verizon. We have escalated this with our carrier partner who is working on the resolution of the issue.
Feb 16, 08:45 PST
Feb 15, 2017
Resolved - This incident has been resolved. All systems operating normally.
Feb 15, 11:39 PST
Monitoring - We are seeing recovery of deliveries to and from a subset of US short codes. Some messages are still queued on the provider side. We expect the queues to drain shortly.
Feb 15, 11:19 PST
Identified - Our monitoring system has detected delays in inbound and outbound messages on a subset of US short codes. We have escalated with our carrier partner and will update as we have more specifics.
Feb 15, 11:01 PST
Resolved - We have fully resolved the issue with the Authy API. Outage window was from 1:44am PST to 2:19am PST (9:44am UTC to 10:19am UTC).
Feb 15, 02:32 PST
Monitoring - We have observed recovery with the Authy API. We are continuing to monitor to ensure full resolution.
Feb 15, 02:24 PST
Investigating - We are experiencing an issue with the Authy API. We are working on resolving the issue. We will provide an update in 15 minutes.
Feb 15, 02:15 PST
Feb 14, 2017

No incidents reported.

Feb 13, 2017
Resolved - We have fully resolved the issue.
Feb 13, 22:40 PST
Monitoring - We have identified the issue impacting a small number (~1%) of requests for Phone Number Updates. We are observing recovery, estimated impact is sub 0.2%. We will continue to monitor the issue to ensure full resolution.
Feb 13, 22:33 PST
Update - Update: We are continuing to investigate an issue impacting a small number (~1%) of requests for Phone Number Updates. We will provide another update in two hours.
Feb 13, 20:25 PST
Update - We are continuing to investigate an issue impacting a small number (~1%) of requests for Phone Number Updates. Next update in two hours.
Feb 13, 18:45 PST
Update - We are continuing to investigate an issue impacting a small number (~1%) of requests for Phone Number Updates. Next update in one hour.
Feb 13, 17:54 PST
Update - We are continuing to investigate an issue impacting a small number (~1%) of requests for Phone Number Updates. Next update one hour.
Feb 13, 17:43 PST
Investigating - We are investigating an issue impacting a small amount (~1%) of requests for Phone Number Updates. Impacted requests are seeing higher latency and errors. We will provide another update in one hour.
Feb 13, 16:46 PST
Resolved - We have resolved the issue fully.
Feb 13, 21:20 PST
Update - Update: We are seeing improvement for the issue impacting inbound calls to numbers in Goiânia (+5562), Brasília (+5561) and Campo Grande (+5567) - Brazil. We are working with our carrier partner to confirm full resolution. We will provide an update in one hour.
Feb 13, 20:26 PST
Identified - We have identified an issue impacting inbound calls to numbers in Goiânia (+5562), Brasília (+5561) and Campo Grande (+5567) - Brazil. Customers may not be able to make or receive calls to or from numbers in these areas. We are working with our carrier partners to resolve the issue. We will provide an update in one hour.
Feb 13, 19:35 PST
Resolved - We have resolved the issue impacting inbound calls in Recife, Brazil (+5581)
Feb 13, 10:41 PST
Investigating - We are currently investigating an issue impacting inbound calls in Recife, Brazil (+5581). We are working with our carrier partners to resolve the issue. We will provide the next update in 1 hour.
Feb 13, 09:15 PST
Feb 12, 2017

No incidents reported.

Feb 11, 2017

No incidents reported.

Feb 10, 2017
Resolved - All systems have recovered.
Feb 10, 11:36 PST
Investigating - We are currently investigating an issue with submitting phone number ports through the Twilio Console.
Feb 10, 11:06 PST
Resolved - All systems have now recovered.
Feb 10, 11:17 PST
Monitoring - We have seen a recovery in receiving calls with Brazil - Rio de Janeiro (+5521) and Jundiai (+55114). Our engineers are continuing to monitor this situation.
Feb 10, 11:01 PST
Investigating - We are currently experiencing a reduced number of completed inbound calls in the areas of Rio de Janeiro and Jundiai. We are actively working with our carrier partners to resolve this issue.
Feb 10, 09:36 PST
Feb 9, 2017

No incidents reported.

Feb 8, 2017
Resolved - All systems are normal.
Feb 8, 21:05 PST
Monitoring - Our system has recovered. All messages are available for lookup. We continue to monitor.
Feb 8, 20:53 PST
Update - Our system has mostly recovered. Roughly 10% of customers will still experience delays retrieving message lists. Our next update will be within two hours.
Feb 8, 18:18 PST
Update - Our system has mostly recovered. Roughly 20% of customers will still experience delays retrieving message lists. We expect recovery within four hours. Our next update will be within four hours.
Feb 8, 13:56 PST
Update - We have identified the issue. Instance fetches are now working properly. The team is working on fixing retrieval of list message resources. Next update within the hour.
Feb 8, 13:12 PST
Identified - We are currently experiencing delays in looking up messages in the Console and REST API. Users looking up messages that have been sent are seeing delays. Our engineering team is looking into the incident and actively working to resolve it. We will post another update within the hour.
Feb 8, 12:48 PST
Resolved - All services are now operating normally.
Feb 8, 19:40 PST
Investigating - We are currently investigating an outage with some of our phone numbers in Mexico being unreachable. We are working with our carrier partner to identify the problem and find a resolution.
Feb 8, 17:38 PST