We are investigating an issue affecting some Formstack Documents workflows that use Formstack Sign. Although signing completes successfully, subsequent deliveries including Salesforce, SharePoint, and webhooks may not be released and may remain in a delayed status. Our team is actively working to resolve the issue. We will provide additional updates as they become available.

We are currently seeing elevated error rates for real device tests in EU-Central-1 data center. We are investigating.

There’s a Salesforce service performance degradation. Users can access the Salesforce service, but some functionality can be unavailable or running at less than optimal performance. General and intermittent slow performance, timeouts, and connectivity issues are possible. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.

Between 15:12 and 15:16 UTC, we observed a brief increase in load on the connection proxy layer in us-east-1, which may have affected some existing and new connections. The team responded quickly and resolved the issue. All systems are now fully operational.

We are investigating reports that some Formstack Sign customers are unable to send documents through the API. Affected requests may return a “Request requires authentication” error despite successfully generating an access token. Some customers may also see a null API secret within their account. Our team is actively investigating and will provide additional updates as more information becomes available.

Some customers are seeing CORS preflight failures when requesting cross-space references on CDA through webbrowsers. We've identified the cause and are working on resolution.

We are investigating an issue affecting Azure OpenAI and Foundry agent services in the Sweden Central region. Impacted customers may experience intermittent errors when making service requests.We are investigating the underlying issue and exploring mitigation options to restore normal service performance. Our analysis remains ongoing, and we are closely monitoring service health while continuing our investigation.We will provide additional information as it becomes available.

This incident has been resolved. Sites on the High-Performance Edge have returned to normal operation, and we are no longer seeing elevated error rates.

There’s a Salesforce service feature degradation. During a feature degradation, some features are unavailable or run at less than optimal performance. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.

Formstack Documents with document deliveries to Formstack Sign are failing as of 11:19pm Eastern on Monday Sept 28. We are investigating the issue and will update accordingly.

We are aware of a feature disruption that may impact you and are currently working on a solution to resolve user impact. During a feature disruption, end users sometimes can’t access certain aspects of the service. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We are investigating reports of impacted performance for some GitHub services.

Future: At approximately 9:30 pm Eastern Time on Monday September 28th, Formstack Sign will undergo a migration to ensure faster and more reliable user authentication. There is no risk to documents in flight, and no risk of account data loss. There could be a small interruption to user sessions during the migration, which is expected to take nearly two hours.

We are currently seeing elevated error rates for automated real device tests in US-West-1 data center. We are currently investigating.

We are currently investigating increased error rates in the EU region affecting uploads (eager transformations), transformations, and delivery. The issue began at approximately 06:15 UTC. We will provide updates as more information becomes available.

We are aware of a service disruption that may impact you and are currently working on a solution to resolve user impact. During a service disruption, end users may not be able to access the service. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We are currently investigating an issue where Figma Services are degraded or unavailable because of failures with AWS and other dependencies.

We are currently investigating this issue.

The Salesforce Technology team identified a disruption affecting Intelligence customers on this instance and is working to resolve it. During a Marketing Cloud Intelligence disruption, end users are unable to access the service. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.

There’s a Salesforce service feature degradation. During a feature degradation, some features are unavailable or run at less than optimal performance. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.

The Salesforce Technology team identified a feature disruption affecting customers on this instance and is working to resolve it. During a Marketing Cloud Engagement feature disruption, end users are unable to access certain aspects of the affected service. We’re investigating the issue and will provide updates as soon as possible. See Impacted Services and Additional Information for further details.

There’s a Salesforce service feature disruption. During a feature disruption, end users sometimes can’t access certain aspects of the service. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.

Status: Fix released with percy/cli v1.32.11 Since 20:48 UTC on September 24, npm install @percy/cli fails with: npm ERR! code EUNSUPPORTEDPROTOCOL npm ERR! Unsupported URL Type "patch:": patch:got@npm%3A11.8.2#... With npm 10 and later, the install can fail with no error message. Cause: A third-party package that the Percy CLI depends on, @yarnpkg/core, published version 4.9.2 with a dependency format that npm can't install. Percy's services are not affected; only new CLI installs are. Fix: We have released a patch version of percy/cli v1.32.11 and now @latest should install correctly Workaround (for earlier percy cli versions): Add this to your project's root package.json: "overrides": { "@yarnpkg/core": "4.9.1" }

We are investigating reports of errors affecting access to Netlify-hosted sites. Our engineering team is actively investigating the issue. We will provide additional updates as more information becomes available.

We are investigating reports of impacted performance for some GitHub services.

We are aware of a feature degradation that may impact customers, and are actively working to resolve user impact. During a feature degradation certain platform features may be intermittently timeout or operate at less than optimal performance. We’ll provide an update in 60 minutes or sooner if additional information becomes available.