TelnyxInbound Calls to Australian DIDs Not Connecting
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Our TTS endpoints for sonic-3.5 experienced degraded performance and queuing between UTC 15:01 and UTC 15:32. We've mitigated the issue and are monitoring the situation.
Resolved
This incident has been resolved.
Resolved
All metrics confirm that the issue impacting GitLab Duo Agent Platform (DAP) is fully resolved, and we're marking this incident as closed. We appreciate your patience while we worked through it.
Resolved
Between 08:30 UTC and 13:51 UTC on 26 May 2026, some users were unable to load or edit certain macros in the Confluence Cloud page editor. Our engineering team identified and resolved the underlying issue, and macro functionality has been fully restored.
Resolved
This incident has been resolved.
Resolved
We have observed no further impact on services during our monitoring period. The Snyk Incident Response has now been stood down.
Resolved
The issue affecting Buffer has been fully resolved. Our team has confirmed that the service is now operating normally. We apologise for any disruption this may have caused and appreciate your patience throughout the resolution process. If you encounter any further issues, please let us know.
Resolved
Access to sentry.io is now fully operational
Resolved
We identified and resolved an issue that could cause endpoint updates to experience delayed propagation after CDN services had been running for an extended period of time. The issue was related to endpoint synchronization between Magic Containers and the CDN routing component, where slower processing connected to sticky session invalidation could result in stale endpoint data remaining in use longer than expected.
Resolved
The issue affecting Buffer has been fully resolved. Our team has confirmed that the service is now operating normally. We apologise for any disruption this may have caused and appreciate your patience throughout the resolution process. If you encounter any further issues, please let us know.
Resolved
The issue affecting database loading has been mitigated and users are now able to load their Notion databases normally.
Resolved
Status Update Our security and operations teams completed the assessment of our infrastructure, which forcd a upcp update today for all systems we were able to reach. We also reviewed environments for the indicators of compromise noted in the LiteSpeed article below. We will address any findings via a support ticket. We are resolving this incident at this time. Customer Guidance Customers are strongly encouraged to ensure they are running the updated version of the LiteSpeed plugin and to review their systems for the indicators of compromise. If our team does not have access to your system because it is unmanaged, self-managed, or access has been updated but not shared with Liquid Web, then we would not have been able to reach your system in order to apply updates or check for indicators of compromise. If you have any questions or concerns, you can reach us through the following channels: Live Chat via the Customer Portal: https://my.liquidweb.com Email: support@liquidweb.com
Resolved
This issue has been resolved.
Resolved
This incident has been resolved.
Resolved
Between 12:30 UTC and 14:15 UTC on May 25, 2026, customers may have experienced failures or delays in compute operations or database connectivity. The issue has been fully resolved, and all services are operating normally. We apologize for any inconvenience. If you require further details, please submit a support ticket.
Resolved
The fix has been successful, and all systems are now operating normally. We will continue to monitor performance closely. Thank you for your patience and understanding as we addressed this issue. If you continue to experience any residual issues or have further questions, please reach out to our team at support@travis-ci.com
Resolved
This incident has been resolved.
Resolved
On May 19, 2026, at 18:26 UTC, we identified an issue impacting the creation and re-provisioning of Linode instances using any of the four RTX PRO 6000 Blackwell \(g3-gpu-rtxpro6000-blackwell\) plans, resulting in API errors. These failures caused a denial of service for customers attempting to deploy g3-gpu-rtxpro6000-blackwell instances via the Cloud Manager or API. After the initial investigation SMEs determined that the cause of the issue was a logic error within a recent APIv4 update. Specifically, a validation check intended only for RDMA-enabled networking was incorrectly applied to standard Blackwell GPU plans. This caused the API to reject creation requests that did not meet specific RDMA configurations, even when those configurations were not required for the selected plan. With the issue identified, our engineering team developed and tested a hotfix to correct the plan-validation logic. Deployment of the fix began shortly after, and broader customer impact was mitigated as of 21:36 UTC on May 19, 2026, following successful verification in all regions. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and we are currently reviewing our automated testing to prevent similar recurrences.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We’re seeing sustained recovery for custom email setup. We are no longer seeing elevated provisioning failures or latency.
Resolved
This incident has been resolved.
Resolved
We observed an increased rate of timeouts for updates manifest requests. This issue has been resolved and the service is stable.
Resolved
Veo 3.1 error rates have returned to normal levels.
Resolved
A INSTABILIDADE NA INTEGRAÇÃO COM A GUPSHUP no RD STATION CONVERSAS foi resolvida com sucesso. Caso você note que sua conta ainda contém alguma inconsistência, por favor, entre em contato com nosso Time de Suporte através da nossa Central de Ajuda "através da nossa Central de Ajuda": http://ajuda.rdstation.com/..
Resolved
This incident has been resolved.
Resolved
All latest emails delivered nominally, any lagged emails will be reattempted and delivered with a delay.
Resolved
The issue affecting GPT Image 2 generations has been resolved. All image generation requests are now processing normally. We apologize for any inconvenience.
Resolved
Task processing in our EU region was briefly delayed from 12:45 to 13:05 UTC after capacity scaled down too far, which slowed some background actions from completing normally. We scaled capacity back up and processing has recovered. Service should now be operating normally.
Resolved
This incident has been resolved.
Resolved
The rollback has completed and the affected hog destinations and workflow steps have returned to normal operation. No further impact. A follow-up fix to the safety guard is in progress and will be re-deployed only after additional validation against production traffic patterns.
Resolved
The issue affecting Text-to-Speech (TTS) generation, which was causing intermittent 500 errors, has been resolved. The service is now operating normally.
Resolved
## Service Impact A subset of our customers experienced elevated latency in our notification delivery, build dispatch and metrics services. ## Incident Summary We are in the process of migrating our underlying compute platform from AWS Fargate to AWS EKS for our production workloads. We are migrating our services in small batches so we can verify stability as we go. Between 15:42 and 17:33 our EKS Prometheus server began to need more memory than was available on the host where it was running. This was caused by autoscaling operations that increased the number of pods tracked by Prometheus, which in turn increased the Prometheus server's memory requirement. The host killed the Prometheus server process, which was restarted shortly after by the Kubernetes control plane. In the interim, the metrics used for application autoscaling were unavailable. The unavailable metrics meant that the affected services were not being triggered to scale up, resulting in the observed delays. Prometheus exceeded the host's available memory again soon after restarting, which caused the cycle to repeat. The on call team followed a prepared documentation to shift load on the affected services back to Fargate. The majority of customers saw complete recovery from 16:49. A handful of customers had developed such a large backlog during the period of higher latency, that they had to be manually scaled up further. All customers saw full recovery by 17:33. ## Changes we're making We have already made the following changes to our rollout of EKS for production workloads: * Upsized the underlying system nodes. * Set higher requests and limits for the Prometheus server so it can handle more product load. * Reviewed and set any missing requests and limits for all new EKS resources, ensuring that EKS has all the required information to prevent accidental resource contention. * Added more observability and monitors for EKS pod and node health to help us identify root causes quickly during future incidents. We have since migrated all these services back to EKS and observed successful scaling well beyond the limits we encountered during this incident.
Resolved
The issue has been resolved, and services are operating normally. No further impact is expected. We’re sorry for any disruption this may have caused and thank you for your patience and understanding.
Resolved
We have resolved the underlying cause of the issue affection service operations in our Azure regions. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.
Resolved
This incident has been resolved.
Resolved