SendGridSMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs to Beeline Kazakhstan
The incident has been resolved and SMS delivery from Twilio to Beeline network subscribers in Kazakhstan is operating normally.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The incident has been resolved and SMS delivery from Twilio to Beeline network subscribers in Kazakhstan is operating normally.
Resolved
The incident has been resolved and SMS delivery from Twilio to Beeline network subscribers in Kazakhstan is operating normally.
Resolved
Vonage services have been fully restored following today’s service interruption, which began at 2026-10-12 21:51:24 UTC. Full resolution has been confirmed effective 2026-10-13 14:28 UTC. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved.
Resolved
The incident is resolved. Error rates are back to normal, and stable service has been confirmed. We will publish a Root cause analysis once our review of the incident is complete.
Resolved
This has been resolved
Resolved
This incident has been resolved.
Resolved
We have confirmed that the upstream Rackspace email service issue has been fully resolved. All services, including webmail portal logins, third-party email clients, and mailbox creation, are now functioning normally. Thank you for your patience during this time.
Resolved
The issue is now resolved fully. Some users saw elevated error rates in Figma's AI features, including AI chat and Figma Make. Affected requests may have failed or needed a retry. We identified an issue with one of our providers and moved traffic to an alternate. Error rates have fully recovered. We are continuing to work with the provider to prevent this from happening again. We apologize for the disruption.
Resolved
This incident has been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved and the backlog of delayed transaction updates has cleared. Some customers may have observed elevated SYNC_UPDATES_AVAILABLE webhook volume while processing caught up. We did not observe an abnormal increase in webhook delivery failures, and no customer action is required.
Resolved
The incident has been resolved and SMS delivery from Twilio to Etisalat and Du network subscribers in the United Arab Emirates is operating normally.
Resolved
The incident has been resolved and SMS delivery from Twilio to Etisalat and Du network subscribers in the United Arab Emirates is operating normally.
Resolved
Fixed the root cause.
Resolved
We haven't observed any additional issues with the Cloud Manager logins, and will now consider this incident resolved. If you continue to experience issues receiving verification codes, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
We would like to inform you that an incident occurred in the GRA4, GRA5, GRA7, GRA9 and GRA11 regions. This incident has now been resolved. Please find the details of this incident below : <b>Start time :</b> 13/10/2026 05:17 UTC <b>End time :</b> 13/10/2026 05:26 UTC <b>Impacted Service(s) :</b> Some instances in the GRA5, GRA7, GRA9 and GRA11 regions were unavailable. <b>Customers Impact :</b> Customers were temporarily unable to access their instances located in the specified regions. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
Resolved
Resolved
Between 03:25 and 04:44 UTC on October 13, 2026, some requests to create an Instant Voice Clone failed with an error. This affected the Voice Lab in the app and the Voices API endpoint (POST /v1/voices/add), when background noise removal was turned on. Clones created without background noise removal weren’t affected.
Resolved
This incident has been resolved.
Resolved
Maintenance ended
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation.
Resolved
The incident has been resolved and SMS delivery from Twilio to Telekom network subscribers in Germany is operating normally.
Resolved
The incident has been resolved and SMS delivery from Twilio to Telekom network subscribers in Germany is operating normally.
Resolved
The issue with Workflows has been resolved, and services are now operating normally. We apologize for any disruption this may have caused and appreciate your patience and understanding.
Resolved
This incident has been resolved.
Resolved
We've become aware of a brief issue in Xero Partner Hub where customers in AU and NZ were experiencing slowness and errors. Our Product Team are investigating what caused this and the Xero Partner Hub is operational now.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The incident has been resolved and SMS delivery from Twilio to Movistar network subscribers in El Salvador is operating normally.
Resolved
The incident has been resolved and SMS delivery from Twilio to Movistar network subscribers in El Salvador is operating normally.
Resolved
The incident has been resolved and MMS delivery from a subset of Twilio Long Codes to C-Spire network subscribers in the United States is operating normally.
Resolved
The incident has been resolved and MMS delivery from a subset of Twilio Long Codes to C-Spire network subscribers in the United States is operating normally.
Resolved
We can confirm that the issue was mitigated at 11:41 UTC on 22 September 2026, and the service has resumed normal operation. We have not observed any related impact to the Akamai platform since the issue self-corrected.We remain in contact with our upstream providers and continue to monitor the related repair work for this incident. Customers and partners can view additional details by logging in to the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V5RQqCAN or by contacting Akamai Support.We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to help prevent recurrence.
Resolved
Query performance is back to normal and the incident is resolved.
Resolved