Website hosting
The servers that host our clients’ websites.
The servers that host our clients’ websites.
Mail our servers send: website forms, notifications and support replies.
Our website, store and customer accounts.
The support site, help articles and request forms.
Sends visitors to a healthy support server: Seattle first, Fremont if Seattle fails.
Sending visitors to Seattle.
Where support normally runs.
Takes over with its own copy of our support data if Seattle fails.
Standing by.
The managed hosting dashboard.
Uptime, mail and security monitoring for hosted sites.
Plugin updates and licensing for hosted sites.
Content tools for client websites.
Email authentication reports for client domains.
Proposals, contracts and signatures.
From their own status pages, for the parts we use. Not counted in our status above.
Our network edge, DNS, load balancer and this page.
Cloudflare reports: Workers: degraded performance.
No services match.
Where our services run. Each data center's server is checked directly every minute, without Cloudflare in between.
Fremont, California
Primary data center · Akamai Cloud, us-west
ServerOperational
Checked directly every minute
Seattle, Washington
Support data center · Akamai Cloud, us-sea
ServerOperational
Checked directly every minute
Juneau, Alaska
Home of the Hoke Designs team
Support is run from here. No servers are hosted in Juneau; our services run in the Fremont and Seattle data centers.
Two data centers on Akamai Cloud, each checked directly every minute. Hover or tap a location for what runs there.
Primary data center · Akamai Cloud, us-west
Server reachability, checked directly
Support data center · Akamai Cloud, us-sea
Server reachability, checked directly
One of our providers reported a delay in a reporting feature unrelated to our services. Our AI content tools were not affected, and no action was needed from customers.
One of our AI providers reports: We have identified an issue causing delays in publishing Organization cost data through the Costs API. Our own checks show our services running normally so far.
One of our providers had a brief problem with a tool used to update our status page. A fix was applied hours ago, and our websites, email and support were not affected. This is resolved.
We've been informed by our network and security provider that a fix has been implemented and they are monitoring the results. This status page is the only thing of ours this touches.
We've been informed by our network and security provider that the cause of the Workers API issue has been identified and a fix is being implemented. This status page is still affected.
We've been informed by our network and security provider that they are investigating an issue affecting their Workers API. Customers may be seeing an increase in 5xx errors when deploying Workers or doing other API actions. This status page is affected.
We've been informed by our network and security provider that the elevated error rate for workers startup has been resolved. This status page was the only item of ours affected.
We've been informed by our network and security provider that there is an elevated error rate for workers startup, affecting workers that use large amounts of memory. They have identified the issue and are working on a solution, and this status page is affected.
We've been informed that one of our AI providers has resolved the issue that was causing elevated errors, as of 6:38 AM AKST on Nov 13. This had been affecting our AI features, which should now be working normally.
We've been informed that one of our AI providers says errors have returned to normal levels and they are continuing to monitor. They report that existing connectors are working again, while adding a new connector is temporarily unavailable and some scheduled tasks have run more than two hours late or been skipped. This may affect our AI features. Our own checks show our services running normally so far.
We've been informed that the provider is seeing recovery, though errors may return while they continue working on this. They say some connected tools and several of their other services remain degraded, and they will share another update soon. This may affect our AI features. Our own checks show our services running normally so far.
We've been informed that the provider's investigation now also covers additional services beyond those reported earlier, and that they are still looking into the degraded performance. This may affect our AI features. Our own checks show our services running normally so far.
One of our AI providers reports: We are investigating reports of degraded performance affecting the provider.ai, the the provider API, the provider Code, and connectors (including the provider Docs and the provider Sheets). Our own checks show our services running normally so far.
We've been informed by one of our AI providers that they are investigating reports of degraded performance and elevated errors. This affects our AI features. The provider said they will share an update as soon as possible. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the incident has been resolved. Voice calls from a subset of phone numbers to subscribers in the United States are operating normally. This was reported at 2:28 PM AKST on Nov 12.
We've been informed by our phone and text provider that they have observed a recovery in voice calls from a subset of phone numbers to subscribers in the United States, and they are monitoring service stability. They will provide another update in 2 hours or as soon as more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that they have identified the cause of the post-dial delay affecting some phone calls to subscribers in the United States, and they are working to resolve it. They expect to post another update in 1 hour or as soon as more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that some phone calls to subscribers in the United States may experience a delay after dialing. They are actively investigating and expect to post another update in 1 hour or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the DNSSEC configuration change issues have been resolved. This touched our DNS, and the provider posted the resolution at 8:26 PM AKST on Nov 11.
We've been informed by our network and security provider that a fix for the DNSSEC configuration change issues has been implemented, and they are now monitoring the results. This touches our DNS, and we're continuing to keep an eye on it. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the issue with DNSSEC configuration changes has been identified and a fix is being implemented. This touches our DNS, and we're continuing to watch it closely. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are continuing to investigate the issue with DNSSEC configuration changes. They have not shared any new details as of 8:00 PM AKST on Nov 11. This touches our DNS, and we're continuing to watch it closely. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating issues with enabling or disabling DNSSEC signing. They are working to understand the full impact and mitigate the problem. This touches our DNS, and we're watching it closely. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the incident has been resolved. Text message delivery to AT&T subscribers in the United States is operating normally, as of their update at 9:02 PM AKST on Nov 11.
We've been informed by our phone and text provider that text message delivery to AT&T subscribers in the United States has recovered, and they are now monitoring service stability. Their next update is expected in 2 hours or as soon as more information becomes available.
We've been informed by our phone and text provider that the cause has been identified and they are still working to resolve the delivery failures affecting text messages to AT&T subscribers in the United States. Their next update is expected in 2 hours or as soon as more information becomes available.
We've been informed by our phone and text provider that text messages sent to AT&T subscribers in the United States may fail to deliver. They have identified the cause and are working to resolve it, and expect to share another update in 1 hour or as soon as more information is available.
We've been informed by our phone and text provider that the issue causing text messages sent from long code numbers to AT&T customers in the US to fail has been resolved. This update was posted at 5:37 PM AKST on Nov 11.
We've been informed by our phone and text provider that text messages sent from long code numbers to AT&T customers in the US are failing to deliver. Their engineers are working with a carrier partner to resolve the issue, and they expect to share another update in 1 hour or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed that one of our AI providers has resolved the elevated errors that affected logins, sign-ups, and chat features. They report that all affected services are operating normally again. This touched our AI content tools.
We've been informed that one of our AI providers is investigating an outage affecting logins and sign-ups, along with elevated error rates when creating conversations. This touches our AI content tools. The provider is checking how users are affected and will share an update when they know more. Our own checks show our services running normally so far.
One of our providers had a problem deploying some security certificates. Certificates already in use were not affected, and our websites kept running normally. The provider has put a fix in place, and this is now resolved.
We've been informed by our network and security provider that a fix has been implemented for the issue affecting security certificates. They posted this update at 12:01 AM AKST on Nov 11 and are now monitoring the results. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the issue affecting security certificates has been identified and a fix is being implemented. They posted this update at 11:17 PM AKST on Nov 10. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating an issue deploying a subset of custom certificates, which touches our security certificates. They advise pausing certificate redeployments until it is resolved, and say certificates already in production are unaffected and operating normally. Our own checks show our services running normally so far.
We've been informed that our network and security provider has resolved the Worker Builds issue. The update was posted at 9:41 PM AKST on Nov 10. This status page was the only item of ours affected.
We've been informed that our network and security provider has implemented a fix for the Worker Builds issue and is now monitoring the results. This status page is still affected. The update was posted at 9:35 PM AKST on Nov 10.
We've been informed that our network and security provider has identified the cause of the Worker Builds issue and is implementing a fix. This status page is still affected. The update was posted at 9:32 PM AKST on Nov 10.
Our network and security provider has informed us that it is investigating an issue with Worker Builds that potentially impacts multiple customers, and this status page is affected. They say existing Workers and Containers are unaffected, and that more detail will be shared as it becomes available.
One of our providers reported a problem with incorrect cost figures in its usage reports. This did not affect our services or any customer websites, and our services kept running normally throughout.
We've been informed that one of our AI providers identified an issue causing incorrect cost data in Costs API exports published between November 6 and 9. They are working to correct the affected records and will share an update once recovery is confirmed. This touches our AI content tools. Our own checks show our services running normally so far.
One of our providers paused a feature we don't use. Our websites, support and this status page were not affected, so we are closing this notice.
We've been informed by our network and security provider that changes to Workers are temporarily not producing Event Subscription events, and that they intentionally disabled the feature due to an ongoing issue. They are working to restore it but say this may take a while. Changes to Workers themselves are working normally, and already deployed Workers are unaffected. This touches this status page.
We've been informed by one of our AI providers that the elevated errors on their API have been resolved and all affected services are operating normally again. This had affected our AI content tools. The provider apologized for the disruption.
We've been informed by one of our AI providers that users are experiencing elevated errors on the impacted services. They have identified the issue and are working on implementing a mitigation. This affects our AI content tools. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the incident causing changes to be delayed or disrupted has been resolved, as of 4:46 PM AKST on Nov 9. This affected this status page.
We've been informed by our network and security provider that changes made to Workers may be delayed or disrupted. They are continuing to monitor for any further issues, as of 7:35 AM AKST on Nov 9. This affects this status page.
One of our providers reported a delay in making changes to a behind-the-scenes tool. Our websites and services kept running normally and were not affected. This notice is now closed.
We've been informed by our network and security provider that changes made to Workers may be delayed or disrupted. They are continuing to monitor for any further issues as of 7:35 AM AKST on Nov 9. This affects this status page.
One of our providers had a brief issue with making changes to one of its tools. Our websites and services were not affected, and the issue is now resolved.
We've been informed by our network and security provider that changes made to Workers may be delayed or disrupted. They are continuing to monitor for any further issues as of 7:35 AM AKST on Nov 9. This affects this status page.
We've been informed by our network and security provider that the network performance issues in Eastern North America have been resolved. The provider posted this update at 11:12 AM AKST on Nov 9. Website delivery, which was affected, is no longer impacted by this incident.
We've been informed by our network and security provider that a fix has been put in place for the network performance issues in Eastern North America, and they are now monitoring for any further issues. This may still affect website delivery. The provider's latest update was posted at 8:21 AM AKST on Nov 9. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they have identified the cause of the network performance issues in Eastern North America and are continuing to work on a fix. This may still affect website delivery. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating network performance issues in Eastern North America. They are working to analyze and mitigate the problem, and this may affect website delivery. Our own checks show our services running normally so far.
One of our providers had a problem that delayed changes to a service on their side. Websites that were already running were not affected. A fix was applied and no further issues have been seen.
We've been informed by our network and security provider that a fix has been put in place and they are now monitoring for any further issues. The incident, which involved changes to Workers being delayed or disrupted, touches this status page.
Our network and security provider reports: We are continuing to work on a fix for the issue.
We've been informed by our network and security provider that they are investigating issues with creating, editing and deleting Workers. They say the impact is limited to making changes, and Workers that are already deployed are unaffected. This touches this status page.
Our code hosting provider reports that the parts of their service we rely on are working normally again, so we are closing this notice. They are still working on a separate part of the issue; if it affects us again, we will post a new notice.
We've been informed by our code hosting provider that the degradation affecting API requests has been mitigated, and they are now monitoring to ensure stability. This was affecting plugin updates. Their update was posted at 2:56 AM AKST. Our own checks show our services running normally so far.
We've been informed by our code hosting provider that they have identified a problematic component and are working to redeploy it. This may still affect plugin updates. Our own checks show our services running normally so far.
We've been informed by our code hosting provider that some unauthenticated users are seeing an increase in timeouts, and that API requests are experiencing degraded performance. They are continuing to investigate. This may affect plugin updates. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that the issue has been resolved. They report the impact occurred from 08:18 UTC to 08:32 UTC on Nov 8. This touched our AI features.
We've been informed by one of our AI providers that a fix has been deployed for the model that was showing degraded performance, and they are monitoring for recovery. This touches our AI features.
We've been informed by one of our AI providers that they are investigating elevated errors on requests to one of their models. This touches our AI features. They have said they will provide an update as soon as possible.
Our phone and text provider reports that the parts of their service we rely on are working normally again, so we are closing this notice. They are still working on a separate part of the issue; if it affects us again, we will post a new notice.
We've been informed that our phone and text provider has seen a recovery in delivery receipts for text messages and is now monitoring service stability. The provider expects to share another update in 2 hours or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed that our phone and text provider has identified the cause of the delivery receipt delays and is working to resolve it. Text messages may still be delivered, but their delivery receipts may be delayed. The provider expects to share another update in 16 hours or sooner if more information becomes available. Our own checks show our services running normally so far.
Our phone and text provider reports: The provider customers may be experiencing SMS delivery receipt delays from a subset of the provider Long Codes and Short Codes to network subscribers on multiple networks in the United States. Our own checks show our services running normally so far.
We've been informed that the provider has identified the cause of the delivery receipt delays and is working to resolve it. Messages may still be delivered, but delivery receipts for our text messages may arrive late. The provider will share another update in 4 hours or as soon as more information is available. Our own checks show our services running normally so far.
Our phone and text provider reports: The provider customers may be experiencing SMS delivery receipt delays from a subset of the provider Long Codes and Short Codes to network subscribers on multiple networks in the United States. Our own checks show our services running normally so far.
We've been informed that our phone and text provider has identified the cause of the delayed delivery receipts and is working to resolve it. The delays now affect a subset of long codes and short codes on multiple US networks. Messages may still be delivered, but receipts may arrive late, and the provider expects to share another update in 1 hour or sooner. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that delivery receipts for text messages may be delayed from a subset of long codes to multiple networks in the United States. Message delivery may still succeed, but the receipts may arrive late. The provider is investigating and expects to share another update in 1 hour or sooner if more information becomes available. Our own checks show our services running normally so far.
This notice turned out to be about a payment-card problem at one of our AI providers, not their service. Our AI content tools were not affected.
We've been informed that one of our AI providers has applied a mitigation for elevated error rates with some U.S. business Mastercards. They are monitoring the affected services to confirm recovery. This touches our AI content tools. Our own checks show our services running normally so far.
One of our AI providers reports: Investigating — We’re seeing payment declines on some U.S. Our own checks show our services running normally so far.
One of our AI providers reports: **Investigating** — We’re seeing payment declines on some U.S. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the incident causing deployment and build failures has been resolved. This status page was the part of our services affected.
We've been informed by our network and security provider that a fix has been implemented for failures affecting deployments and builds. They are monitoring the results. This status page is the part of our services affected.
Our phone and text provider reports that the parts of their service we rely on are working normally again, so we are closing this notice. They are still working on a separate part of the issue; if it affects us again, we will post a new notice.
We've been informed by our phone and text provider that they have seen a recovery in voice calls from a subset of Canadian phone numbers to Rogers Wireless and Fido subscribers in Canada, and they are now monitoring stability. This may still affect our phone calls. The provider will share another update in 2 hours or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that they are still working to resolve post dial delay on voice calls from a subset of Canadian phone numbers to subscribers in Canada. This may affect our phone calls. The provider now expects to share another update in 2 hours or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that some calls from a subset of Canadian phone numbers to subscribers in Canada are experiencing post dial delay. This may affect our phone calls. The provider says the cause has been identified and they are working to resolve it, with another update expected in 1 hour or sooner. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the network latency issue in NRT has been resolved. Their update was posted at 6:33 AM AKST on Nov 4. This had touched website delivery.
We've been informed by our network and security provider that a fix has been implemented for the network latency issue in NRT, and they are now monitoring the results. This still touches website delivery. Their update was posted at 6:19 AM AKST on Nov 4. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the cause of the network latency issue in NRT has been identified and a fix is being implemented. This still touches website delivery. Their update was posted at 5:58 AM AKST on Nov 4. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating a network latency issue in NRT. This touches website delivery. We'll share more as we hear from them. Our own checks show our services running normally so far.
We've been informed by our code hosting provider that the incident with pull requests, Git operations and issues has been resolved. The update was posted at 2:50 AM AKST. This had been affecting our plugin updates.
We've been informed by our code hosting provider that the degradation affecting Actions has been mitigated, and they are monitoring to ensure stability. This may still affect our plugin updates while they monitor. The update was posted at 2:43 AM AKST. Our own checks show our services running normally so far.
We've been informed by our code hosting provider that the degradation affecting API requests, Git operations, issues and pull requests has been mitigated, and they are monitoring to ensure stability. This may still affect our plugin updates while they monitor. The update was posted at 2:30 AM AKST. Our own checks show our services running normally so far.
We've been informed by our code hosting provider that they are working on mitigating elevated errors and intermittent failures affecting pull requests, Git operations, and issues. Some requests may fail or be delayed, which may affect our plugin updates. The provider has said they will share another update as more information becomes available. Our own checks show our services running normally so far.
We've been informed by our code hosting provider that API requests are experiencing degraded performance, and they are continuing to investigate. This may affect our plugin updates. Our own checks show our services running normally so far.
We've been informed that the incident affecting API and Git requests has been resolved. This had touched our plugin updates. The provider says a detailed root cause analysis will be shared once it is available.
Our code hosting provider reports: The degradation has been mitigated. Our own checks show our services running normally so far.
Our code hosting provider reports: API Requests is operating normally. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the network performance issues in the APJC region have been resolved. This was posted at 8:56 PM AKST on Nov 2. Website delivery was the part of our service that could have been affected.
We've been informed by our network and security provider that a fix has been implemented for the network performance issues in the APJC region, and they are now monitoring the results. Website delivery may still be affected while they monitor. We're continuing to watch our services. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the cause of the network performance issues in the APJC region has been identified and a fix is being implemented. This may still affect website delivery. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating network performance issues in the APJC region. They are working to analyze and mitigate the problem, and this may affect website delivery. They expect to share more updates shortly. Our own checks show our services running normally so far.
Our phone and text provider reports that the parts of their service we rely on are working normally again, so we are closing this notice. They are still working on a separate part of the issue; if it affects us again, we will post a new notice.
We've been informed by our phone and text provider that voice call audio has recovered, and they are now monitoring service stability. This may still affect our phone calls while they watch. They expect to share another update in 2 hours or as soon as more information is available.
We've been informed by our phone and text provider that voice calls may be experiencing audio delays and high packet loss, which may affect our phone calls. They are actively investigating and expect to share another update in 1 hour or as soon as more information is available.
Our phone and text provider reports that the text message delays lasted about an hour and service has been stable since, with no messages lost. Our own services were not affected, so we are closing this notice.
We've been informed that our phone and text provider is still validating a permanent fix for the single-host issue that delayed text messages. Service remains stable, and they say there was no data loss. Their next update is expected in 16 hours or sooner if there is new information.
We've been informed that our phone and text provider traced the text message delays to an issue with a single host, which affected only a portion of SMS traffic for approximately one hour. Service has been restored and stable since, with no data loss. They have applied a preventive measure, are validating a permanent fix, and will share their next update in 8 hours or sooner if there is new information.
We've been informed that our phone and text provider has posted a new update on the delays affecting text messages. They are still investigating the root cause, and they expect to provide another update in 8 hours or as soon as more information becomes available.
We've been informed that our phone and text provider has identified and mitigated the issue causing delays in text messages, and that no messages were lost. They are still investigating the root cause. Their next update is expected in 4 hours or as soon as more information becomes available.
We've been informed that our phone and text provider is still investigating the root cause of the delays in text messages. They continue to say the issue has been mitigated and no messages were lost. Their next update is expected in 2 hours or as soon as more information becomes available.
We've been informed by our phone and text provider that they have identified and mitigated the issue causing the delays in text messages. They say no messages were lost, and they are still investigating the root cause. They expect to provide another update in 1 hour or as soon as more information becomes available.
We've been informed by our phone and text provider that they are investigating delays affecting text messages, and that no messages are lost. They expect to provide another update in 1 hour or as soon as more information becomes available. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the incident causing delayed Worker deployments has been resolved. This had touched this status page.
We've been informed by our network and security provider that some customers may see delays when deploying updates to Workers, and that remediation is in progress. This touches this status page.
We've been informed that one of our AI providers has resolved the elevated errors on image edit requests, and all affected services are operating normally again. This affected our AI content tools. Their update was posted at 10:36 AM AKDT.
We've been informed that the provider has applied a mitigation for the elevated errors on image edit requests and is now monitoring the affected services to confirm recovery. This affects our AI content tools. Their update was posted at 8:06 AM AKDT. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that some image edit requests are seeing elevated errors. They have identified the issue and are working on a fix. This affects our AI content tools. Our own checks show our services running normally so far.
Our phone and text provider reports that the parts of their service we rely on are working normally again, so we are closing this notice. They are still working on a separate part of the issue; if it affects us again, we will post a new notice.
We've been informed that our phone and text provider has observed a recovery in text message delivery to Altice network subscribers in the United States. They are monitoring service stability and expect to share another update in 2 hours, or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed that our phone and text provider has identified the cause of the delays affecting text messages sent to Altice network subscribers in the United States. They are working to resolve the issue and expect to share another update in 16 hours, or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed that our phone and text provider is still working to resolve the delays affecting text messages sent to Altice network subscribers in the United States. They now expect to share another update in 8 hours, or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed that our phone and text provider has identified the cause of the delays affecting text messages sent to Altice network subscribers in the United States. They are working to resolve it and expect to share another update in 4 hours, or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed that our phone and text provider is still working to resolve delays affecting text messages sent to Altice network subscribers in the United States. They now expect to share another update in 2 hours, or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that text messages sent to Altice network subscribers in the United States may be delayed. They say the cause has been identified and they are working to resolve it, with another update expected in 1 hour or sooner if more information becomes available. Our own checks show our services running normally so far.
Our network and security provider has closed this notice on their side, so we are closing ours too.
We've been informed by our network and security provider that success rates for Workflows operations have been dipping since approximately 07:00 UTC, and customers may see increased errors or failures when running workflows. They are investigating the root cause. This affects this status page.
Our phone and text provider reports that the parts of their service we rely on are working normally again, so we are closing this notice. They are still working on a separate part of the issue; if it affects us again, we will post a new notice.
We've been informed that voice calls from a subset of the provider's phone numbers to subscribers in the United States are recovering, and they are monitoring service stability. This affects our phone calls. They will provide another update in 2 hours or as soon as more information becomes available. Our own checks show our services running normally so far.
Our phone and text provider reports: The provider customers may be experiencing voice call failures from a subset of the provider Phone Numbers to network subscribers in the United States. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that some voice calls from a subset of phone numbers to T-Mobile subscribers in the United States may be failing, which affects our phone calls. They have identified the cause and are working to resolve it, and expect to share another update in 1 hour or sooner if more information becomes available. Our own checks show our services running normally so far.
Our phone and text provider reports that the parts of their service we rely on are working normally again, so we are closing this notice. They are still working on a separate part of the issue; if it affects us again, we will post a new notice.
We've been informed by our phone and text provider that voice calls from a subset of phone numbers to T-Mobile subscribers in the United States are recovering, and they are monitoring service stability. This may affect our phone calls. The provider expects to share another update in 2 hours or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that they have identified the cause of the voice call failures from a subset of phone numbers to T-Mobile subscribers in the United States, and are working to resolve it. This may affect our phone calls. The provider expects to share another update in 1 hour or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that voice calls from a subset of phone numbers to T-Mobile subscribers in the United States may be failing. This may affect our phone calls. The provider is actively investigating and expects to share another update in 1 hour or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the issue with shortened links on some branded short domains has been resolved. Their engineers monitored the fix and confirmed that all services are now operating normally. This had touched our text messages.
We've been informed by our phone and text provider that a fix has been implemented for the shortened link errors, and they are now monitoring system performance. This touches our text messages. The provider expects to share another update in 30 minutes or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that shortened links on some branded short domains are intermittently returning errors and may not redirect when opened in Chrome. This touches our text messages. The provider is investigating and rolling out a fix, and expects to share another update in one hour or sooner. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that customers in the Australia region are no longer encountering 503 errors for messaging traffic, and the incident has been resolved. This was the issue that could affect our text messages.
We've been informed by our phone and text provider that a fix has been deployed for the 503 errors affecting messaging traffic in the Australia region, and its engineers are now monitoring to confirm the errors have stopped. Our text messages may still be affected in the meantime. The provider expects to share another update in 30 minutes or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that its engineers have identified the cause of the 503 errors affecting messaging traffic for some customers in the Australia region and are continuing to work on deploying a fix. Our text messages may be affected. The provider expects to share another update in 4 hours or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that engineers are still working to deploy a fix for 503 errors affecting messaging traffic for some customers in the Australia region. Our text messages may be affected. The provider expects to share another update in 2 hours or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that some customers in the Australia region may see 503 errors with messaging traffic. They have identified the issue and are working to deploy a fix, and expect to share another update in 1 hour or as soon as more information is available. This may affect our text messages. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that the issue causing elevated errors has been resolved. They reported that impact occurred from 07:42 PT / 14:42 UTC to 08:17 PT / 15:17 UTC. Our AI features were affected during that time.
We've been informed by one of our AI providers that they are seeing elevated errors on some requests, and our AI features may be affected. They are investigating and will share an update as soon as possible.
We've been informed that the incident has been resolved. MMS delivery from a subset of long codes to AT&T subscribers in the United States is operating normally, so our text messages are no longer affected.
We've been informed that MMS delivery from a subset of long codes to AT&T subscribers in the United States has recovered, and our provider is now monitoring service stability. This may still affect our text messages. They expect to provide another update in 2 hours or sooner if more information becomes available.
We've been informed that the issue behind delayed MMS messages from a subset of long codes to AT&T subscribers in the United States has been identified, though their team is still investigating. This may affect our text messages. They expect to provide another update in 2 hours or sooner if more information becomes available.
Our phone and text provider reports: Wilio customers may be experiencing MMS delivery delays from a subset of the provider Long Codes to AT&T network subscribers in the United States. Our own checks show our services running normally so far.
We've been informed that the issue is now narrowed to MMS delivery delays from a subset of long codes to AT&T subscribers in the United States. Their team is still investigating and expects to post another update in 2 hours or sooner if there is more information. This affects our text messages. Our own checks show our services running normally so far.
Our phone and text provider reports: The provider customers may be experiencing SMS and MMS delivery delays from a subset of the provider Long Codes to AT&T network subscribers in the United States. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that delivery receipts for some text messages sent to AT&T subscribers in the United States may be delayed. They say messages may still be delivered, and they are actively investigating. Their next update is expected in 1 hour or sooner if they learn more. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that the issue behind the elevated errors has been resolved. This had been affecting our AI features.
We've been informed by one of our AI providers that a fix has been deployed for the issue behind the elevated errors, and they are now monitoring for recovery. This may still affect our AI features while they do. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that they are investigating elevated errors on requests to one of their models. This may affect our AI features. They have said they will share an update as soon as possible. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the incident causing some customers' Pages and/or workers builds to fail intermittently has been resolved. This had affected this status page.
We've been informed by our network and security provider that a fix has been implemented and they are monitoring the results. This still affects this status page. We'll share another update when the provider reports further changes.
We've been informed by our network and security provider that the cause has now been identified. They report that some customers may see cloning of GitHub repositories fail, which is why builds are intermittently failing. This affects this status page.
We've been informed by our network and security provider that some customers may notice their Pages and/or workers builds are intermittently failing. They are currently investigating the issue. This affects this status page.
Our phone and text provider reports that the parts of their service we rely on are working normally again, so we are closing this notice. They are still working on a separate part of the issue; if it affects us again, we will post a new notice.
We've been informed that our phone and text provider has seen a recovery in delivery receipts for text messages sent to AT&T subscribers in the United States, and they are monitoring service stability. They expect to share another update in 2 hours or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed that the provider has now identified the cause of the delivery receipt delays and is working to resolve it. Messages may still be delivered even though receipts may be delayed. The provider expects to share another update in 1 hour or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed that the delays affect only a subset of the provider's long codes sending to AT&T subscribers in the United States. They are still investigating, and message delivery may succeed even though receipts may be delayed. The provider now expects to share another update in 2 hours or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that delivery receipts for text messages sent to AT&T subscribers in the United States may be delayed. Message delivery may still succeed, but the receipts may arrive late. They are investigating and expect to share another update in 1 hour or sooner. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the issue with scheduled tasks running late, being skipped, or running more than once has been resolved. This touched this status page.
We've been informed by our network and security provider that they are now monitoring the issue with scheduled tasks running late, being skipped, or running more than once. They are continuing to monitor for any further issues. This touches this status page.
We've been informed by our network and security provider that they are investigating reports of some scheduled tasks running late, being skipped, or running more than once. This touches this status page. The provider will post an update as they learn more.
We've been informed that our code hosting provider has resolved the incident that affected Actions, Issues, API requests and pull requests. This touches our plugin updates. The provider says a detailed root cause analysis will be shared once it is available.
We've been informed that our code hosting provider saw elevated latency from 17:59 UTC to 18:40 UTC, during which some requests were slow or timed out and notifications were delayed. They report the issue has been mitigated and all services have recovered, and they are still monitoring. This touches our plugin updates. Our own checks show our services running normally so far.
We've been informed that our code hosting provider has mitigated the degradation affecting API requests, Actions, Issues and Pull Requests. They are monitoring to ensure stability. This touches our plugin updates. Our own checks show our services running normally so far.
We've been informed that our code hosting provider is investigating reports of degraded performance for API requests, Actions, Issues and Pull Requests. This touches our plugin updates. The provider posted this update at 10:48 AM AKDT on Oct 26. Our own checks show our services running normally so far.
One of our AI providers reports: The issue affecting the provider services has been resolved.
We've been informed by one of our AI providers that a fix has been deployed for the issue causing elevated errors, and they are now monitoring for recovery. This affects our AI features. The update was posted at 12:30 AM AKDT on Oct 25. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that they have identified the cause of elevated errors on some requests and are working on a fix. This affects our AI features. The provider has said they will share an update as soon as possible. Our own checks show our services running normally so far.
One of our AI providers reports that the parts of their service we rely on are working normally again, so we are closing this notice. They are still working on a separate part of the issue; if it affects us again, we will post a new notice.
We've been informed by one of our AI providers that a fix has been deployed for the issue causing elevated errors, and they are now monitoring for recovery. This may still affect our AI features while recovery is confirmed. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that they have identified the cause of the elevated errors affecting one of their models and are working on a fix. This may affect our AI features. The provider has said they will share an update as soon as possible. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that they are investigating elevated errors on requests to several of their models. This may affect our AI features. The provider has said they will share an update as soon as possible. Our own checks show our services running normally so far.
Our phone and text provider reports that the parts of their service we rely on are working normally again, so we are closing this notice. They are still working on a separate part of the issue; if it affects us again, we will post a new notice.
We've been informed that our phone and text provider has observed a recovery in voice calls from a subset of phone numbers to subscribers in the United States, and is now monitoring service stability. This affects phone calls. The provider will share another update in 2 hours or as soon as more information becomes available. Our own checks show our services running normally so far.
We've been informed that our phone and text provider is still working to resolve the voice call failures and post dial delay, and has now said the next update will come in 8 hours or sooner if more information becomes available. This affects phone calls. Our own checks show our services running normally so far.
We've been informed that our phone and text provider has identified the cause of the voice call failures and post dial delay affecting a subset of phone numbers calling subscribers in the United States. They are working to resolve it and will provide another update in 4 hours or sooner if more information becomes available. This affects phone calls. Our own checks show our services running normally so far.
Our phone and text provider reports: The provider customers may be experiencing voice call failures and post dial delay from a subset of the provider Phone Numbers to network subscribers in the United States. Our own checks show our services running normally so far.
We've been informed that the provider has identified the cause of the voice call failures and post dial delay affecting a subset of phone numbers calling US subscribers, and is working to resolve it. This touches our phone calls. The provider will share another update in 1 hour or as soon as more information is available. Our own checks show our services running normally so far.
Our phone and text provider reports: The provider customers may be experiencing voice call failures from a subset of the provider Phone Numbers to network subscribers in the United States. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that some phone calls from a subset of their phone numbers to subscribers in the United States may be failing. Our phone calls may be affected. The provider is actively investigating and expects to share another update in 1 hour or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed that the issue causing elevated errors has been resolved. The provider reported impact from 22:00 PT on October 23 / 05:00 UTC on October 24 to 22:35 PT on October 23 / 05:35 UTC on October 24. This affected our AI features.
We've been informed that a fix has been deployed for the issue behind the elevated errors, and the provider is now monitoring for recovery. This affects our AI features. We'll post another update once the provider reports further progress. Our own checks show our services running normally so far.
One of our AI providers reports: We have identified the cause of elevated errors on requests to other the provider models and are working on a fix. Our own checks show our services running normally so far.
We've been informed that our AI provider has identified the cause of the elevated errors on requests to some of their models and is working on a fix. Our AI features may be affected. The provider has said it will share another update as soon as possible. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that they are investigating elevated errors on requests to some of their models. Our AI features may be affected. The provider has said it will share an update as soon as possible. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the network performance issues in Ashburn have been resolved. This had been affecting website delivery. The update was posted at 7:09 PM AKDT on Oct 23.
We've been informed by our network and security provider that a fix has been implemented for the network performance issues in Ashburn, and they are now monitoring the results. This may still affect website delivery while they monitor. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they have posted a list of the specific services affected by the network performance issues in Ashburn. They are still investigating, and this may affect website delivery. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating network performance issues in Ashburn, VA. This may affect website delivery. They are working to analyze and mitigate the problem and have said more updates will follow shortly. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that the issue causing elevated errors has been resolved. They said the impact ran from 00:23 UTC to 00:34 UTC on October 24. Our AI features were the part of our services this could have touched.
We've been informed by one of our AI providers that they are investigating elevated errors on requests to one of their models. This may affect our AI features. The provider has said it will share an update as soon as possible. Our own checks show our services running normally so far.
One of our AI providers reports: The issue affecting the provider models has been resolved.
We've been informed that our AI provider is seeing success rates return to normal for all affected models. They are continuing to monitor to make sure no further issues come up. Our AI features were touched by this, and we're keeping an eye on them as well. Our own checks show our services running normally so far.
We've been informed that our AI provider has identified the cause of the elevated errors on requests to several of their models and is working on a fix. Our AI features may be affected. They have said they will share another update as soon as possible. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that they are investigating elevated errors on requests to one of their models. This may affect our AI features. They have said they will share an update as soon as possible. Our own checks show our services running normally so far.
We've been informed that our network and security provider has resolved the network connectivity issues affecting services in North America. This had been affecting website delivery. The resolution was posted at 10:43 AM AKDT.
We've been informed that our network and security provider has rerouted traffic around the impacted paths and is no longer seeing packet drops. Their connectivity provider reports its service has been restored, but some links are still being brought back, so traffic management changes remain in place. This affects website delivery, and the update was posted at 10:18 AM AKDT. Our own checks show our services running normally so far.
We've been informed that our network and security provider's team is continuing traffic engineering actions to route around impacted paths, which affects website delivery. They will keep doing this until all packet drops are mitigated. This update was posted at 9:33 AM AKDT. Our own checks show our services running normally so far.
We've been informed that our network and security provider's infrastructure provider has experienced a recurrence of the failure. Our provider is continuing to apply traffic management actions to further remediate the issue, which affects website delivery. This update was posted at 9:03 AM AKDT. Our own checks show our services running normally so far.
We've been informed that our network and security provider is continuing to work on a fix for the connectivity issues in North America. This affects website delivery. The update was posted at 8:59 AM AKDT, and it follows the earlier report that a fix was in place and being monitored. Our own checks show our services running normally so far.
We've been informed that our network and security provider has implemented a fix for the connectivity issues in North America and is now monitoring the results. This affects website delivery. The update was posted at 8:27 AM AKDT. Our own checks show our services running normally so far.
Our network and security provider reports: We have identified a connectivity provider outage causing network congestion and degraded performance for some customers in North America. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating degraded network performance affecting some traffic between their Ashburn and Atlanta data centers. Some traffic in the Eastern US may see increased latency, packet loss, or intermittent errors, which can touch website delivery. Their network team is actively working on mitigation. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the incident affecting scheduled tasks, which were running late, being skipped, or running more than once, has been resolved. This update was posted at 12:37 PM AKDT on Oct 23. It affected this status page.
We've been informed by our network and security provider that a fix has been implemented for the scheduled tasks that were running late, being skipped, or running more than once. They are now monitoring the results, and this affects our status page.
We've been informed by our network and security provider that some scheduled tasks are running late, being skipped, or running more than once. They are investigating, and this affects our status page. We'll share more as we hear it.
We've been informed by our phone and text provider that this incident has been resolved. They described it as a duplicate, and said their team is working on separate delivery report delays to multiple small networks in the United States and Canada.
We've been informed by our phone and text provider that they have identified the cause of the delays affecting text messages to Appalachian Wireless subscribers in the United States. They are working to resolve it and expect to share another update in 1 hour or as soon as more information is available.
We've been informed by our phone and text provider that text messages sent to subscribers on the Appalachian Wireless network in the United States may be delayed. The provider is actively investigating and expects to share another update in 1 hour or as soon as more information is available.
Our phone and text provider reports that the parts of their service we rely on are working normally again, so we are closing this notice. They are still working on a separate part of the issue; if it affects us again, we will post a new notice.
We've been informed by our phone and text provider that delivery receipts for text messages have recovered on multiple networks in North America, and they are monitoring service stability. They will share another update in 2 hours or as soon as more information is available.
Our phone and text provider reports: The provider customers may be experiencing SMS delivery receipt delays from the provider to network subscribers on multiple networks in multiple countries in North America.
We've been informed by our phone and text provider that their cause has been identified and they are working to resolve the delivery receipt delays on multiple networks in the United States and Canada. Messages may still be delivered, but delivery receipts may be delayed. Their next update is expected in 2 hours or sooner.
We've been informed by our phone and text provider that the delivery receipt delays now also reach multiple networks in Canada, in addition to those in the United States. They say messages may still be delivered, but delivery receipts may be delayed. The provider has identified the cause and is working to resolve it, with another update expected in 1 hour or sooner. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the delivery receipt delays now affect subscribers on multiple networks in the United States, not only one. They say message delivery may still succeed, but receipts may be delayed. The provider has identified the cause, is working to resolve it, and expects to post another update in 1 hour or sooner. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that delivery receipts for text messages sent to Altice subscribers in the United States may be delayed. Messages may still be delivered, and the provider says it has identified the cause and is working to resolve it. They expect to share another update in 1 hour or sooner if more information is available. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the access service incident has been resolved. This issue had affected secure sign-in to our hubs. The provider posted the resolution at 1:22 AM AKDT on Oct 23.
We've been informed by our network and security provider that a fix has been implemented for the access service issue, and they are now monitoring the results. This issue has affected secure sign-in to our hubs. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the issue with their access service has been identified and a fix is being implemented. This continues to affect secure sign-in to our hubs. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating issues with their access service when used with Microsoft Entra ID. This affects secure sign-in to our hubs. They are working to understand the full impact and mitigate the problem. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the incident causing elevated errors for some requests in Ashburn, Virginia has been resolved. This had touched website delivery and this status page. The resolution was reported at 9:31 AM AKDT on Oct 22.
We've been informed by our network and security provider that some requests handled by their Ashburn, Virginia data center are seeing elevated error rates (HTTP 502), which may cause failed or intermittent responses. This touches website delivery and this status page. They are investigating, and we'll share more as we learn it. Our own checks show our services running normally so far.
Our code hosting provider reports that the parts of their service we rely on are working normally again, so we are closing this notice. They are still working on a separate part of the issue; if it affects us again, we will post a new notice.
We've been informed that our code hosting provider has mitigated the degradation that delayed project updates, and they are now monitoring to ensure stability. Plugin updates are the part of our work this touches. The provider posted this update at 4:55 PM AKDT on Oct 22. Our own checks show our services running normally so far.
We've been informed that the provider's processing of project updates has improved, but newly added items may still take longer than expected to appear. They are continuing to work on the remaining delays and monitor recovery. Plugin updates are the part of our work this touches. Our own checks show our services running normally so far.
We've been informed that the provider has seen some recovery, though some project updates, including newly added items and changes to issues and pull requests, are still delayed. They are working to add more capacity to speed up the recovery. Plugin updates are the part of our work this touches. Our own checks show our services running normally so far.
We've been informed that the provider has identified interruptions in update processing, which is why some project updates, including newly added items and changes to issues and pull requests, remain delayed. They are evaluating mitigations to restore normal operation. Plugin updates are the part of our work this touches. Our own checks show our services running normally so far.
We've been informed that some project updates tied to issue changes and merged pull requests are still delayed. Our code hosting provider is investigating the remaining delays and working to restore normal processing. Plugin updates are the part of our work this touches. Our own checks show our services running normally so far.
We've been informed that some updates in our code hosting provider's project tracking service are still delayed. They are continuing mitigation work and monitoring. Plugin updates are the part of our work this touches. Our own checks show our services running normally so far.
We've been informed that the other affected services have recovered. Our code hosting provider is continuing to investigate one remaining service and verify that normal operation has been restored. Plugin updates are the part of our work this touches. Our own checks show our services running normally so far.
Our code hosting provider reports: We're seeing recovery across the affected services. Our own checks show our services running normally so far.
Our code hosting provider reports: Actions, Issues, Packages and Pull Requests are operating normally. Our own checks show our services running normally so far.
We've been informed by our code hosting provider that errors are decreasing after they added capacity. Some users may still see errors loading Issues, Pull Requests and search results, and they are continuing to work toward full recovery while monitoring for stability. This touches our plugin updates. Our own checks show our services running normally so far.
We've been informed by our code hosting provider that some users still see errors loading Issues, Pull Requests, package listings and search results. They are working through multiple mitigation efforts and continuing to investigate. This touches our plugin updates. Our own checks show our services running normally so far.
We've been informed by our code hosting provider that API Requests is now operating normally. They are still investigating the errors loading Issues, Pull Requests, and search results. This touches our plugin updates. Our own checks show our services running normally so far.
We've been informed by our code hosting provider that Packages is now experiencing degraded performance, in addition to the earlier errors. They are continuing to investigate. This touches our plugin updates. Our own checks show our services running normally so far.
We've been informed by our code hosting provider that API requests are experiencing degraded performance, with errors loading Issues, Pull Requests, and search results. They are continuing to investigate. This touches our plugin updates. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the increased latency issue has been resolved. This touched this status page.
We've been informed by our network and security provider that they are now monitoring the increased latency issue and continuing to watch for any further problems. This touches this status page.
We've been informed by our network and security provider that they are seeing increased latency when interacting with the Workers API and Workers configuration in the dashboard, with longer wait times possible, particularly when deploying a script. They say Workers already running in production are not affected. This touches this status page.
We've been informed by one of our AI providers that the elevated errors have been resolved, and all impacted services have fully recovered. The provider posted this update at 12:50 AM AKDT on Oct 22. This had been affecting our AI content tools.
We've been informed by one of our AI providers that they have applied a mitigation for the conversion failures in India, Japan and Korea and the Response API errors, and are monitoring the recovery. This may affect our AI content tools. The provider posted this update at 6:42 PM AKDT on Oct 21. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that they are investigating conversion failures in India, Japan and Korea, along with Response API errors. This may affect our AI content tools. The provider posted this update at 6:18 PM AKDT on Oct 21. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that the issue affecting their other models has been resolved. This touches our AI features. The provider posted this update at 12:29 PM AKDT on Oct 21.
We've been informed by one of our AI providers that they are investigating elevated errors on requests to one of their models. This touches our AI features. The provider has said it will share an update as soon as possible. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the increased latency in India has been resolved. This had touched website delivery. We have nothing further to report on this incident.
We've been informed by our network and security provider that a fix has been identified and implemented for the increased latency in India. The provider is now monitoring the results. This touches website delivery. Our own checks show our services running normally so far.
We've been informed by our network and security provider that some traffic in India is experiencing increased latency, which may mean slower loading times. This touches website delivery. The provider's engineering teams are investigating. Our own checks show our services running normally so far.
We've been informed that one of our AI providers has confirmed the elevated error rates are resolved, and all impacted services have fully recovered. This affected our AI content tools. The update was posted at 8:44 AM AKDT on Oct 21.
We've been informed that our AI provider has applied the mitigation for the elevated error rates and is now monitoring the recovery. This touches our AI content tools, and we're continuing to watch it closely.
We've been informed by one of our AI providers that they have identified the cause of elevated errors affecting some of their services, and they are working on implementing a mitigation. This touches our AI content tools, and we're watching it closely.
We've been informed that one of our AI providers has fully recovered from the elevated API error rates, as of 11:34 AM AKDT. This issue has been resolved. It touched our AI content tools.
As of 8:46 AM AKDT, we've been informed that one of our AI providers has applied a mitigation for the elevated API error rates and is monitoring the recovery. This touches our AI content tools. We're continuing to watch our own services closely. Our own checks show our services running normally so far.
At 5:51 AM AKDT, one of our AI providers posted that it is investigating the elevated API error rates for the affected services. This touches our AI content tools. We're continuing to watch our own services closely. Our own checks show our services running normally so far.
We've been informed that one of our AI providers has identified elevated errors affecting some of its services. This touches our AI content tools. The provider is working on implementing a mitigation. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the DNS update delays have been resolved. This affected DNS changes. The update was posted at 3:50 AM AKDT on Oct 19.
We've been informed by our network and security provider that they are now monitoring for any further issues with the DNS update delays. This affects DNS changes. This update was posted at 3:39 AM AKDT on Oct 19. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the cause of the DNS update delays has been identified and they are continuing to work on a fix. This continues to affect DNS changes on our end. This update was posted at 3:35 AM AKDT on Oct 19. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating delays in the propagation of updates to DNS records. This affects DNS changes on our end. They have said more updates will follow shortly. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the incident has been resolved. This issue had touched secure sign-in to our hubs. Their update was posted at 11:09 AM AKDT.
We've been informed by our network and security provider that a fix has been implemented and they are monitoring the results. This issue still touches secure sign-in to our hubs. Their update was posted at 11:02 AM AKDT. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the issue has been identified and a fix is being implemented. This still affects secure sign-in to our hubs. We'll post again when they report further progress. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating issues with accessing their dashboard and related access services, which affects secure sign-in to our hubs. They report that serving of cached files and other security features at the edge are not affected, and that they have identified the issue and are working on a fix. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the issue delaying A2P 10DLC campaign approvals has been resolved. Campaign status is operating normally, and text messages are no longer affected.
We've been informed by our phone and text provider that campaign status is now operating normally again, and they are monitoring for system stability. This affects text messages. Their next update is expected in 30 minutes, or as soon as more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that their engineering team is still working on the issue keeping recently approved campaigns from moving to approved, which affects text messages. Their next update is expected in 4 hours, or as soon as more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that their engineering team is continuing to address the issue keeping recently approved campaigns from moving to approved, which affects text messages. They will provide another update in 2 hours, or as soon as more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that an issue is preventing recently approved campaigns from moving from in-progress to approved. This affects text messages. They will provide another update in 1 hour, or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the incident has been resolved. It had touched secure sign-in to our hubs. Their update was posted at 1:59 AM AKDT on Oct 16.
We've been informed by our network and security provider that the fix has been put in place and they are now monitoring for any further issues. This still touches secure sign-in to our hubs. We're keeping an eye on it as well. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the cause of the availability issues has been identified and a fix is being implemented. This still touches secure sign-in to our hubs. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating availability issues affecting login after sign-in. This touches secure sign-in to our hubs. They are working to understand the full impact and mitigate the problem, and more updates are expected shortly. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the scheduled task (cron trigger) issues have been resolved, and the triggers have stabilized as of 5:06 PM AKDT on Oct 15. This touched this status page.
We've been informed by our network and security provider that a fix for the scheduled task (cron trigger) problem has been put in place and they are monitoring for any further issues. This still touches this status page. We'll post again if anything changes.
We've been informed by our network and security provider that some customers may not have their scheduled tasks (cron triggers) invoked. This affects this status page. The provider says it is working to mitigate the problem and more updates will follow.
We've been informed by our network and security provider that the network performance incident in Eastern North America has been resolved. Website delivery is the part of our service this touched. The provider posted the resolution at 1:38 PM AKDT on Oct 15.
We've been informed by our network and security provider that their engineering teams are continuing to remediate the network performance issue, and that no customer impact is being seen at this time. The provider's status is now monitoring. Website delivery is the part of our service this touches. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they have identified an issue with network performance affecting their Ashburn and Newark facilities. Website delivery may see elevated latency or errors for traffic handled by these facilities until it is resolved. The provider is working on a fix and says more updates will follow shortly. Our own checks show our services running normally so far.
We've been informed that our phone and text provider has resolved the incident, and voice calls from a subset of numbers to affected networks in multiple countries are operating normally. The issue was a post-dial delay on those calls. This affected phone calls.
We've been informed that our phone and text provider is still monitoring service stability after the recovery in voice calls, and has now said its next update will come in 4 hours or as soon as more information is available. The original issue was a post-dial delay on calls from a subset of numbers. This affects phone calls. Our own checks show our services running normally so far.
We've been informed that our phone and text provider has observed a recovery in voice calls from a subset of numbers to subscribers on multiple networks in multiple countries. They are now monitoring service stability and plan to share another update in 2 hours or as soon as more information is available. This affects phone calls. Our own checks show our services running normally so far.
We've been informed that our phone and text provider is still working to resolve post dial delay on voice calls from a subset of numbers to multiple networks in multiple countries. They now plan to share another update in 2 hours or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed that our phone and text provider has identified the cause of the post dial delay affecting phone calls and is working to resolve it. They plan to share another update in 1 hour or as soon as more information is available. Our own checks show our services running normally so far.
Our phone and text provider reports: The provider customers may be experiencing voice call post dial delay from a subset of the provider Toll-Free Numbers, Landline Numbers, and Mobile Numbers to network subscribers on multiple networks in multiple countries. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that some phone calls are experiencing a delay after dialing, affecting a subset of numbers on multiple networks in multiple countries. The provider says it has identified the cause and is working to resolve it. They will provide another update in 1 hour or as soon as more information becomes available. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the incident causing availability issues in Norway has been resolved. It affected this status page. Their update was posted at 1:26 PM AKDT on Oct 15.
We've been informed by our network and security provider that a fix has been applied and they are now monitoring for any further issues. The availability problems in Norway affected this status page. We'll share more if anything changes.
We've been informed by our network and security provider that the issue has been identified and they are continuing to work on a fix. The availability problems in Norway are still ongoing. This touches this status page.
We've been informed by our network and security provider that they are investigating reports that pages.dev subdomains are not available in Norway. Sites using custom domains are not impacted. This touches this status page.
We've been informed by our network and security provider that the DNS update delays have been resolved. This touched DNS changes. The provider posted this update at 10:19 AM AKDT on Oct 15.
We've been informed by our network and security provider that a fix for the DNS update delays has been implemented and they are now monitoring the results. This still touches DNS changes. The provider posted this update at 8:27 AM AKDT on Oct 15.
We've been informed by our network and security provider that the cause of the DNS update delays has been identified and a fix is being implemented. This continues to affect DNS changes. The provider posted this update at 8:13 AM AKDT on Oct 15.
We've been informed by our network and security provider that they are investigating delays in the propagation of DNS record updates in multiple regions. This affects DNS changes. They have said more updates will follow shortly.
We've been informed by our network and security provider that the incident causing increased HTTP 502 errors has been resolved. Their update was posted at 12:39 PM AKDT on Oct 15. This had touched website delivery.
We've been informed by our network and security provider that they have moved to monitoring and are continuing to watch for any further issues with the increased HTTP 502 errors. This still touches website delivery. Their latest update was posted at 3:41 AM AKDT on Oct 15. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the cause of the increased HTTP 502 errors has been identified, and they are continuing to work on a fix. This still touches website delivery. Their latest update was posted at 3:27 AM AKDT on Oct 15. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating an increased level of HTTP 502 errors. This touches website delivery. They are working to analyze and mitigate the problem, and more updates are expected shortly. Our own checks show our services running normally so far.
We've been informed that all impacted services have now fully recovered, and the delayed Costs data issue from one of our AI providers has been resolved. This touched our AI content tools.
We've been informed that a fix has been deployed and the provider is monitoring recovery. Costs data in their Compliance API is still delayed while they process the backlog. This touches our AI content tools, and they will provide further updates as processing catches up. Our own checks show our services running normally so far.
One of our AI providers reports: We have identified an issue causing delays in publishing organization cost data through the Costs API. Our own checks show our services running normally so far.
One of our AI providers reports: We have identified an issue causing delays in publishing organization cost data through the Costs API. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that the issue with limited availability on two of their image models has been resolved, and all impacted services have fully recovered. This touches our AI content tools. The provider posted this update at 2:58 AM AKDT on Oct 14.
We've been informed by one of our AI providers that they have applied a mitigation and are monitoring the recovery. This touches our AI content tools. The provider posted this update at 2:40 AM AKDT on Oct 14. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that they are investigating limited availability of two of their image generation models in their API. This touches our AI content tools. The provider posted this update at 2:18 AM AKDT on Oct 14. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the issue with scheduled triggers has been resolved. Their backlogs have cleared and appear healthy, and schedules should be executing as expected. They noted that some schedule redeploys may be required for a small fraction of those affected. This touched this status page.
We've been informed by our network and security provider that they are now monitoring the issue with scheduled triggers and continuing to watch for any further issues. This touches this status page.
We've been informed by our network and security provider that a fix has been identified for the issue with recently created or modified scheduled triggers, and that work on it is underway. This touches this status page.
We've been informed by our network and security provider that they are investigating an issue where recently created or modified scheduled triggers may not run as expected. Existing schedules that haven't been recently changed are not affected. This touches this status page, and the provider is working to identify the cause.
We've been informed by our network and security provider that the cron trigger activation issues have been resolved, as of 4:09 PM AKDT on Oct 13. This affected this status page.
We've been informed by our network and security provider that a fix has been put in place for the cron trigger activation issues, and they are now monitoring for any further issues. This affects this status page.
We've been informed by our network and security provider that the cause of the cron trigger activation issues has been identified and a fix is being implemented. This affects this status page.
We've been informed by our network and security provider that the Cron Trigger activation issues have been resolved. This touches this status page.
We've been informed by our network and security provider that a fix has been implemented for the Cron Trigger issues, and they are now monitoring the results. This touches this status page.
We've been informed by our network and security provider that they are investigating issues with Cron Trigger schedules that were recently created or modified, which may not be executing as expected. Pre-existing schedules that have not been recently modified are not affected. This touches this status page, and the provider is working to identify the cause.
We've been informed by our network and security provider that the performance issues have been resolved. Website delivery was the part of our service affected. The provider posted this update at 3:49 PM AKDT on Oct 12.
We've been informed by our network and security provider that the cause of the performance issues has been identified and they are continuing to work on a fix. Website delivery is the part of our service affected by this. We'll share more as the provider updates us. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating intermittent performance issues affecting some of their data centers. Website delivery may see errors or increased latency, and the provider says it is working to mitigate the issue. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the incident with their Workers API has been resolved. This had touched this status page.
We've been informed by our network and security provider that a fix has been implemented for the 504 errors with their Workers API, and they are monitoring the results. This touches this status page.
We've been informed by our network and security provider that they are investigating 504 errors when using their Workers API and Workers configuration in the dashboard. Some Workers endpoints may be unavailable, particularly when deploying a script, while Workers already running in production are not affected. This touches this status page.
We've been informed by our network and security provider that the network performance issues in Queretaro have been resolved, as of 11:10 AM AKDT on Oct 9. This had been affecting website delivery.
We've been informed by our network and security provider that they have identified the cause of the network performance issues in Queretaro and applied a fix. They are now monitoring the results. This may still affect website delivery. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating network performance issues in their Queretaro facility. They are working to analyze and mitigate the problem, and this may affect website delivery. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that the incident involving delayed Costs data in the Compliance API has been resolved. They report that all impacted services have fully recovered. This affected our AI content tools.
One of our AI providers reports: We have implemented a mitigation, and delayed Costs data is now processing through the Compliance API. Our own checks show our services running normally so far.
One of our AI providers reports: Some customers may continue to experience delayed Costs data through the Compliance API. Our own checks show our services running normally so far.
One of our AI providers reports: We have identified an issue causing delays in publishing Costs data through the Compliance API. Our own checks show our services running normally so far.
One of our AI providers reports: We have identified an issue causing delays in publishing organization cost data through the Costs API. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the incident has been resolved. Text message delivery to Verizon subscribers in the United States is operating normally.
We've been informed by our phone and text provider that text message delivery to Verizon subscribers in the United States has recovered, and they are monitoring for stability. Their next update is expected in 2 hours, or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that their update posted at 2:50 PM AKDT says the cause has been identified and they are still working to resolve the delays. Their next update is expected in 4 hours, or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the delays affecting text messages to Verizon Wireless subscribers in the United States are still being worked on. They have identified the cause and are working to resolve it. Their next update is expected in 2 hours, or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that text messages sent to Verizon Wireless subscribers in the United States may be delayed. They have identified the cause and are working to resolve it, and expect to share another update in 1 hour or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed that our phone and text provider has fully recovered from the delivery issues, and all impacted services are back to normal performance. The incident is now resolved, and text messages are no longer affected.
We've been informed that our phone and text provider is seeing recovery from the intermittent delivery issues across the impacted regions. They are continuing to monitor the services to ensure a full recovery and expect to post another update in 30 minutes or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed that our phone and text provider is seeing recovery for verification traffic, and that their engineers are actively working on a mitigation to restore full service for text message delivery. They expect to post another update in 4 hours or sooner if more information becomes available. Our own checks show our services running normally so far.
Our phone and text provider reports: We have identified the issue affecting the provider Verify and Programmable SMS delivery across impacted regions. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that they have identified the issue affecting text message delivery in impacted regions. They are seeing recovery for verification traffic and are working on mitigation to restore full service for the rest. They expect to share another update in 1 hour or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the incident has been resolved. Delivery receipts for SMS and MMS text messages to AT&T subscribers in the United States are operating normally again.
Our phone and text provider reports: We have observed a recovery in SMS and MMS delivery receipts from the provider to AT&T network subscribers in the United States and are monitoring service stability. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that delivery receipts for text and picture messages to AT&T subscribers in the United States have recovered. They are monitoring to make sure service stays stable and expect to share another update in 2 hours or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that delivery receipts for text messages sent to AT&T subscribers in the United States may be delayed. They have identified the cause and are working to resolve it, and they now expect to share another update in 2 hours or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that text messages sent to AT&T subscribers in the United States may be delayed. They have identified the cause and are working to resolve it, and expect to share another update in 1 hour or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed that our phone and text provider has resolved the incident, and text and picture message delivery to AT&T subscribers in the United States is operating normally. This affected text messages, including delivery receipts.
We've been informed that our phone and text provider has seen a recovery in text and picture message delivery to AT&T subscribers in the United States, and they are monitoring to confirm service stays stable. They expect to post another update in 2 hours or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed that our phone and text provider has identified the cause of the delays in text message and MMS delivery and delivery receipts between them and the AT&T network in the United States. They are working to resolve it and expect to post another update in 1 hour or sooner if more information becomes available. Our own checks show our services running normally so far.
Our phone and text provider reports: The provider customers may be experiencing SMS delivery delays and delivery failures between the provider and AT&T network subscribers in the United States. Our own checks show our services running normally so far.
Our phone and text provider reports: The provider customers may be experiencing SMS and MMS delivery delays and delivery failures between the provider and AT&T network subscribers in the United States. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that text messages between their network and AT&T subscribers in the United States may be delayed. They are actively investigating and will provide another update in 1 hour or as soon as more information is available. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the network performance issues in Columbus have been resolved. Website delivery is the part of our service this touched.
We've been informed by our network and security provider that a fix has been implemented for the network performance issues in Columbus, and they are now monitoring the results. Website delivery is the part of our service this touches. We're continuing to watch our services closely. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the cause of the network performance issues in Columbus has been identified and a fix is being implemented. Website delivery may still be affected. We're continuing to watch our services closely. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are investigating network performance issues in Columbus, OH. This may affect website delivery. They are working to analyze and mitigate the problem, and we're watching our services closely. Our own checks show our services running normally so far.
We've been informed that one of our AI providers has resolved the issues affecting their agents API and computer use. They report that all impacted services have fully recovered as of 12:00 PM AKDT on Oct 6. Our AI content tools were affected by this incident.
We've been informed that one of our AI providers is investigating issues with their agents API and computer use. This affects our AI content tools. We'll share more as the provider updates us.
We've been informed by one of our AI providers that the errors processing large PDFs have been resolved. They reported at 12:11 PM AKDT on Oct 6 that all impacted services have fully recovered, and our AI content tools are no longer affected.
We've been informed by one of our AI providers that the cause of the errors processing large PDFs has been identified and they are implementing the mitigation. This continues to affect our AI content tools. The provider posted this update at 8:39 AM AKDT on Oct 6. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that they are investigating errors when processing large PDFs. This affects our AI content tools. The provider posted this update at 7:45 AM AKDT on Oct 6. Our own checks show our services running normally so far.
We've been informed by our network and security provider that the network routing issue has been resolved. This update was posted at 7:33 AM AKDT on Oct 6. Website delivery is the part of our service it touched.
We've been informed by our network and security provider that a fix has been applied for the network routing issue and they are now monitoring for any further issues. Website delivery is the part of our service this touches. Our own checks show our services running normally so far.
We've been informed by our network and security provider that they are continuing to work on a fix for the network routing issue, which has now been identified. Website delivery may still be affected. Our own checks show our services running normally so far.
We've been informed by our network and security provider that a network routing issue is causing errors for some requests to origins hosted on Microsoft Azure. This may affect website delivery. The provider's team is actively working on remediation. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that the issue causing elevated errors on one of their models has been resolved. This had been affecting our AI features. The provider posted this update at 4:43 AM AKDT on Oct 6.
One of our AI providers has told us they have identified the cause of the elevated errors on requests to one of their models and are working on a fix. This may affect our AI features. The provider has said they will share another update as soon as possible. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that they are investigating elevated errors on requests to one of their models. This may affect our AI features. The provider has said they will share an update as soon as possible. Our own checks show our services running normally so far.
We've been informed that our AI provider has resolved the elevated errors, and all impacted services have fully recovered. The provider's update was posted at 7:17 PM AKDT on Oct 5. Our AI content tools were the part of our services this touched.
We've been informed that our AI provider has applied a mitigation for the elevated errors and is now monitoring the recovery. This may still affect our AI content tools while recovery continues. The provider's update was posted at 6:44 PM AKDT on Oct 5. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that they are seeing elevated errors across several of their services, and they are investigating. This may affect our AI content tools. We'll share more as we hear it. Our own checks show our services running normally so far.
We've been informed by one of our AI providers that the elevated errors in their login and administration APIs have been resolved, and all impacted services have fully recovered. This affected our AI content tools. The update was posted at 5:35 PM AKDT on Oct 5.
We've been informed by one of our AI providers that a fix has been applied for elevated errors in their login and administration APIs, and they are monitoring the recovery. This affects our AI content tools. The update was posted at 4:40 PM AKDT on Oct 5. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the incident has been resolved. Text message delivery from a subset of long code numbers to AT&T subscribers in the United States is operating normally.
We've been informed by our phone and text provider that text delivery from a subset of long code numbers to AT&T subscribers in the United States has recovered. They are monitoring service stability and expect to share another update in 2 hours, or sooner if they learn more. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the delays affect only a subset of long code numbers sending to AT&T subscribers in the United States. They are still investigating and now expect to share another update in 2 hours, or sooner if they learn more. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that some text messages sent to AT&T subscribers in the United States may be delayed. They are actively investigating and expect to share another update in 1 hour or sooner if they learn more. Our own checks show our services running normally so far.
One of our AI providers reports: The issue affecting the provider Mythos 5.1 and the provider Fable 5.1 has been resolved.
We've been informed by one of our AI providers that they are investigating elevated errors on some requests. Our AI features may be affected. They have said they will provide an update as soon as possible. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the data processing delay in the Ireland region has been resolved. Messaging logs, status callbacks, and SMS delivery updates there are operating normally, which covers our text messages. This update was posted at 3:04 AM AKDT on Oct 5.
We've been informed by our phone and text provider that the data processing delay in the Ireland region is now operating normally. This touches our text messages. They will continue to monitor for system stability and will provide another update in 1 hour or as soon as more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the data processing delay in the Ireland region also affects Messaging Insights and SMS delivery updates, in addition to what we shared earlier. This touches our text messages. They are still investigating and will provide another update in 1 hour or as soon as more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that they are investigating a data processing delay affecting messaging logs, status callbacks, and internally routed messages in the Ireland region. This touches our text messages. They expect to share another update in 1 hour or sooner if more information becomes available. Our own checks show our services running normally so far.
We've been informed by our phone and text provider that the incident causing delays for some text messages sent to AT&T subscribers in the United States has been resolved. They report that text message delivery is operating normally again.
We've been informed by our phone and text provider that some text messages sent to AT&T subscribers in the United States may be delayed. The provider has identified the cause and is working to resolve it, and expects to share another update in 1 hour or sooner if more information becomes available. Our own checks show our services running normally so far.
No incidents match these filters.