Resolved -
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Dec 4, 05:26 GMT
Update -
Twilio are experiencing Increased latency and DynamoDB timeouts across roles and realms. Twilio engineers are working to resolve the issue. We will provide another update in 30 minutes or as soon as more information becomes available.
Dec 4, 02:17 GMT
Investigating -
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
Dec 4, 02:14 GMT
Resolved -
The YouSign incident has been resolved, and the service is operating normally.
Dec 3, 15:58 GMT
Monitoring -
A fix for the issue has been implemented, and the team is monitoring the service.
Dec 3, 14:39 GMT
Investigating -
YouSign is currently experiencing a service interruption. The engineering team has identified the issue and is working on a fix. Further updates will be issued as soon as more information becomes available.
Dec 3, 14:35 GMT
Resolved -
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Dec 2, 11:05 GMT
Update -
All applications (including API) are currently unavailable since 11:32 CET. YouSign engineers are actively working on the issue.
We will keep you updated as soon as we have any further information.
Dec 2, 10:49 GMT
Investigating -
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
Dec 2, 10:41 GMT
Resolved -
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Dec 2, 10:09 GMT
Investigating -
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
Dec 2, 10:05 GMT
Resolved -
We are pleased to inform you that the issue affecting Twilio services has been fully resolved. Twilio engineering teams have observed a complete recovery in service performance, with latency levels returning to normal and 500 errors no longer occurring. We will continue to monitor all services closely to ensure ongoing stability. Thank you for your patience and understanding during this time. If you experience any further issues, please do not hesitate to reach out to our support team.
Nov 30, 13:16 GMT
Update -
Twilio are observing a continued recovery in Twilio services and noticing improvements in latency levels, which remain significantly reduced. Twilio will keep monitoring all services to ensure a full recovery and will provide another update in 24 hours or as soon as more information becomes available.
Nov 29, 15:52 GMT
Update -
Twilio are observing a continued recovery in Twilio services and noticing improvements in latency levels, which remain significantly reduced. Twilio will keep monitoring all services to ensure a full recovery and will provide another update in 12 hours or as soon as more information becomes available.
Nov 29, 06:54 GMT
Monitoring -
Twilio are observing a continued recovery in Twilio services and noticing improvements in latency levels, which remain significantly reduced. Twilio will keep monitoring all services to ensure a full recovery and will provide another update in 1 hour or as soon as more information becomes available.
Nov 28, 23:55 GMT
Investigating -
After a period of monitoring, Twilio continue observing degradation of the service. Twilio are observing latency and 5xx errors again. Twilio engineers are working to resolve the issue. Customers may see the updates to accounts balance and usage summary on the billing console being delayed, this will be completed shortly after we implement the fix to resolve the original issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
Nov 28, 22:19 GMT
Update -
Twilio engineers are observing a continued recovery in Twilio services and noticing improvements in latency levels, which remain significantly reduced. Twilio will keep monitoring all services to ensure a full recovery and will provide another update in 4 hours or as soon as more information becomes available.
Nov 28, 20:05 GMT
Monitoring -
We are observing a recovery in Twilio services and noticing improvements in latency levels, which have decreased substantially. We will continue to monitor all services to ensure a full recovery and will provide another update in 30 minutes or as soon as more information becomes available.
Nov 28, 17:19 GMT
Update -
We are continuing to investigate this issue.
Nov 28, 15:58 GMT
Update -
We are continuing to investigate this issue.
Nov 28, 15:58 GMT
Update -
Twilio are experiencing an issue with multiple Twilio services creating high latency and 500 errors. Their engineering team is actively working to resolve the issue. We expect to provide another update in 30 minutes or as soon as more information becomes available.
Nov 28, 15:50 GMT
Investigating -
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
Nov 28, 15:46 GMT
Resolved -
Following comprehensive monitoring, Intermittent call/message orchestration has been resolved, and Flex is operating normally at this time.
Nov 28, 12:29 GMT
Monitoring -
Flex is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.
Nov 28, 12:16 GMT
Update -
Twilio engineers are investigating intermittent call/message orchestration with Flex. We expect to provide another update in 1 hour or as soon as more information becomes available.
Nov 28, 11:28 GMT
Investigating -
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
Nov 28, 11:26 GMT
Resolved -
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Nov 27, 11:05 GMT
Monitoring -
Since 09:10 (CET), all services have returned to normal functionality, the delay has been recovered.
Yousign Engineering teams are now analysing the root cause of the incident. At this stage, the issue appears to be linked to an impact on their provider’s infrastructure. They will conduct a joint analysis with their provider to confirm and understand the sequence of events.
This incident remains in active monitoring.
Nov 27, 08:36 GMT
Update -
Since 08:36 (CET), access to Yousign products v2 and v3 has been degraded, affecting both the applications and the API. This may subsequently impact your current service.
Yousign engineering teams are actively investigating to identify the root cause and restore normal service as quickly as possible.
We will provide updates as the situation evolves.
Nov 27, 08:02 GMT
Investigating -
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
Nov 27, 07:54 GMT
Resolved -
The issue with the Flex customers being unable to connect has been resolved. Flex services are operating normally at this time.
Nov 25, 21:48 GMT
Update -
Twilio continue to observe recovery and their engineering teams are closely monitoring to ensure recovery is sustained and systems remain stable. We expect to provide another update in 1 hour or as soon as more information becomes available.
Nov 25, 18:21 GMT
Monitoring -
Twilio engineering team has identified the issue and fixed it and we are currently observing positive signs of recovery. They are continuing to monitor the system closely to ensure stability over the next 4 hours. During this time, some customers may experience session logouts. If this occurs, please log back in. We do not anticipate any additional errors. We expect to provide another update in 2 hours or as soon as more information becomes available
Nov 25, 16:46 GMT
Identified -
Twilio engineers have identified the issue impacting Flex customers. This issue would result in customers being unable to login to Flex. They may also experience web socket connection errors, or customers could have seen the following error: ‘We have detected a problem with the service’. Their engineering teams are actively working to restore full service as quickly as possible. We expect to provide another update in 30 minutes or as soon as more information becomes available.
Nov 25, 15:42 GMT
Update -
Twilio are currently investigating an issue impacting multiple Flex customers who are unable to connect to Twilio servers. Twilio engineering teams are actively working to identify the root cause and restore full service as quickly as possible. We understand the critical nature of this disruption and apologise for the inconvenience.
Nov 25, 15:00 GMT
Update -
Twilio engineering team is actively investigating an issue with Flex Instances and Taskrouter. We will provide another update in 1 hour or as soon as we have additional information.
Nov 25, 14:49 GMT
Update -
Twilio monitoring systems have detected a potential issue with Flex instances. Twilio engineering team has been alerted and is actively investigating. We will update as soon as we have more information.
Nov 25, 14:38 GMT
Investigating -
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
Nov 25, 14:33 GMT
Resolved -
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Nov 20, 23:27 GMT
Monitoring -
Twilio engineers have deployed a fix and are monitoring performance. Please note that this issue impacted webhook responses and did not impact Voice calls. Twilio is hoping to provide next update in 30 minutes.
Nov 20, 23:02 GMT
Update -
We are continuing to investigate this issue.
Nov 20, 22:56 GMT
Investigating -
We are currently aware of issues affecting inbound and outbound call handling for customers using Twilio Voice. Calls may fail, and webhook requests may return error code 15000. This issue originates from Twilio’s platform and is actively being investigated on their side.
Our systems are operating normally, but affected workflows may experience disruptions due to Twilio’s degraded service. We will provide updates as more information becomes available.
Nov 20, 22:52 GMT