DocuSign Outage History
Daily status observations, past incidents, and reported issue history for DocuSign.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 60% | 25 | 10 |
| July 2026 | 41.9% | 31 | 18 |
| June 2026 | 20% | 30 | 24 |
| May 2026 | 60% | 5 | 2 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Daily Status (Last 91 Days)
May 27
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
Issues in JP1 with Salesforce Writeback (Incident 5648)
Started:
JP1
investigating
Customers in JP1 may experience issues when writing back to Salesforce after signing a document. Engineering teams are engaged and are actively triaging this issue.
Document Upload and Generation Errors (Incident 5595)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Degraded Task Processing and Latency across multiple services (Incident 5576)
Started:
monitoring
We continue to monitor the environment to ensure stability.
monitoring
We continue to monitor the environment to ensure stability.
identified
We continue to work to implement a fix for the issue.
identified
Our initial fix did not fully mitigate this issue. Our teams are continuing to work to implement a fix to resolve the issue.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and we continue our work to implement a fix.
identified
We have identified the issue and a fix is being implemented.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating issues where some customers may see latency or failures when generating documents. Engineering teams have been engaged and are actively triaging.
Login Issues in AU region (Incident 5572)
Started:
monitoring
Our engineering teams have deployed a fix to the affected environments and we are monitoring our telemetry to validate.
identified
Our engineering teams have identified the potential cause of this issue and we are in the process of deploying a fix.
investigating
Some customers may be experiencing issues when attempting to sign in to Docusign in the AU region. Engineering teams have been engaged and we are actively triaging this issue.
Latency and Errors Across NA11 (Incident 5558)
Started:
monitoring
The fix was implemented and we are monitoring to ensure stability.
identified
The issue has been identified and we continue our work to implement a fix.
monitoring
A fix has been implemented and we are monitoring the results.
identified
Customers across NA11 are seeing latency and delays across the service. We have identified the underlying issue and are taking action to mitigate the issue.
Docusign Admin Intermittently Unavailable (Incident 5548)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and we continue our work to implement a fix.
identified
We have identified the issue and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Workflow Send and Review Errors (Incident 5532)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue and a fix is being implemented.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Customers may experience issues accessing the eSign Admin Settings page (Incident 5527)
Started:
identified
The issue has been identified and we continue our work to implement a fix.
identified
We have identified the issue and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are investigating this issue.
Document generation failures in salesforce integration (Incident 5525)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
Customers may encounter document generation failures with salesforce integration.
We are currently investigating the issue.
Powerforms Intermittently Not Loading (Incident 5517)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are actively investigating this issue.
July 2026
Failures with Envelope Writeback and Status Updates (Incident 5505)
Started:
identified
The issue has been identified and we continue our work to implement a fix.
identified
We have identified the issue and a fix is being implemented.
investigating
We are currently investigating an issue affecting customers using the Salesforce integration across EU and NA regions. Customers may experience failures with envelope write-back and status updates, with the error: "The underlying connection was closed. An unexpected error occurred on send."
Services affected: Salesforce connector (envelope write-back, status updates)
Impact: Completed envelope statuses may not be reflected in Salesforce.
Our engineering teams are actively investigating th...
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We are continuing to investigate this issue.
investigating
Customers in Europe may experience failures with envelope writeback and status update when reviewing Connect logs for DAL envelopes. Engineering teams are engaged and are actively triaging.
Latency and Intermittent Errors (Incident 5501)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue and a fix is being implemented.
investigating
We are actively investigating this issue.
Customers may experience errors when signing up for new accounts (Incident 5500)
Started:
identified
We have identified the issue and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Inbound email not may be working for some customers (Incident 5475)
Started:
investigating
We are actively investigating this issue.
Qualified Verification Latency (Incident 5472)
Started:
identified
Customers may be experiencing issues when attempting qualified verifications. Engineering teams have been engaged and are actively triaging this issue.
Customers in AU/JP may experience errors or delays when logging in, sending, or signing envelopes (Incident 5409)
Started:
investigating
AU and JP are stable at present. Teams are continuing to investigate the issue.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Customers may be unable to complete purchases on ecom.docusign.com (Incident 5438)
Started:
identified
The issue has been identified and we continue our work to implement a fix.
identified
We have identified the issue and a fix is being implemented.
investigating
We are actively investigating this issue.
Customers may experience errors loading PowerForms to sign envelopes (Incident 5417)
Started:
identified
We have identified the issue and a fix is being implemented.
investigating
We are actively investigating this issue.
Customers may experience errors executing workflows and uploading documents (Incident 5386)
Started:
identified
We have identified the issue and a fix is being implemented.
investigating
We are actively investigating this issue.
Some Document Generation customers are being redirected to the CLM home page (Incident 5384)
Started:
identified
We have identified the issue and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Some customers (including Notary customers) may not be able to authenticate via LexisNexis' Knowledge-Based Authentication, leading to failure in signing envelopes. (Incident 5383)
Started:
investigating
LexisNexis is continuing to investigate the issue.
investigating
LexisNexis is continuing to investigate the issue.
investigating
LexisNexis has been made aware of the issue and are currently investigating.
Some customers may not able to open any CLM documents (Incident 5375)
Started:
identified
We have identified the issue and a fix is being implemented.
Errors accessing the sending web application (Incident 5334)
Started:
investigating
We continue to investigate with our CDN partner to determine why a very small group of end users are seeing errors. Disabling browser cache completely or completely emptying browser cache and trying again will unblock users. Please contact docusign support if you need assistance.
An update will be provided when a significant update is available.
investigating
We continue to investigate with our CDN partner to determine why a very small group of end users are seeing errors. Disabling browser cache completely or completely emptying browser cache and trying again will unblock users. Please contact docusign support if you need assistance.
An update will be provided when a significant update is available.
investigating
We are continuing to investigate the web cache issue. A small subset of customers may see an error when accessing the send web application page. Completely emptying the browser cache and trying again is a viable fix.
Updates will be posted when there is a significant update.
investigating
We continue to investigate and have engaged external vendor resources
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We are continuing to investigate this issue.
investigating
A small subset of customers may see errors accessing the sending web application. We are actively investigating the underlying cause.
Intermittent Issues With Delivery of e-mail Notifications (Incident 5326)
Started:
identified
A subset of customers may experience intermittent failures of email notifications upon sending of envelopes. To mitigate this customers can log into their DocuSign account and access the envelope directly. Engineering teams have identified the issue and are currently working to resolve this issue.
Intermittent Errors and Delays (Incident 5312)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are actively investigating this issue.
June 2026
Customers may experience latency (Incident 5259)
Started:
identified
We have identified the issue and a fix is being implemented.
investigating
We continue to investigate the issue and additional resources have been engaged. We will provide the next update in approximately 24 hours.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Some customers may experience errors with Sending and Signing (Incident 5252)
Started:
identified
We have identified the issue and a fix is being implemented.
investigating
We are actively investigating this issue.
Customers may experience errors with Sending and Signing in NA3 (Incident 5247)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Intermittent issues with Reports and Search on S1 Prod (Incident 5233)
Started:
investigating
We are currently investigating issues with both report and search on S1 prod. Engineering teams have been engaged and are actively triaging.
Intermittent issues with Reports and Search on S1 Prod (Incident 5233)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating issues with both report and search on S1 prod. Engineering teams have been engaged and are actively triaging.
Customers may see increased latency when sending and signing and intermittent errors (Incident 5232)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
We continue to work to implement a fix for the issue.
identified
The issue has been identified and we continue our work to implement a fix.
identified
We have identified the issue and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Intermittent Errors and Delays (Incident 5219)
Started:
identified
We have identified the issue and a fix is being implemented.
investigating
We are actively investigating this issue.
Some customers may experience latency for any sending actions that involve conversions, generating documents and accessing tasks (Incident 5190) (Incident 5209)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue and a fix is being implemented.
Some customers may experience latency for any sending actions that involve conversions, generating documents and accessing tasks (Incident 5190)
Started:
identified
We have identified the issue and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Platform Latency in UAT (Incident 5187)
Started:
monitoring
Fix has been implemented and we are now monitoring telemetry to validate.
identified
We have identified the source of the issue and are preparing a fix.
investigating
Customers may be experiencing latency on the platform in the UAT Environment. Engineers have been engaged and are actively triaging this issue.
Users downloading archived document ZIP files may see missing official Docusign platform seals (Incident 5139)
Started:
identified
The fix is still in progress and being deployed. We will provide an update upon resolution.
identified
An issue has been identified where documents downloaded via archived ZIP files with "masked fields" enabled are missing their Docusign platform seals. A fix is underway. We will provide an update upon resolution.
Target Fix Date: June 23, 2026
Temporary Workaround: Download documents individually rather than as an archived ZIP file to ensure platform seals are successfully applied.
Salesforce for Gen customers may be unable to generate documents (Incident 5132)
Started:
monitoring
We continue to monitor the environment to ensure stability.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are actively investigating this issue.
Salesforce for Gen customers are unable to generate documents (Incident-5122)
Started:
identified
We are continuing to work on a fix for this issue.
identified
We have identified the issue and a fix is being implemented.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Customers may experience intermittent latency (Incident 5118)
Started:
investigating
We continue to investigate the issue. Performance has improved but the issue is still under investigation.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Users may experience performance latency when utilizing the doc2pdf service (Incident 5085)
Started:
identified
We are have identified the root cause and we are implementing a fix.
Email notifications sent from custom domains may not be delivered (Incident 5106)
Started:
investigating
We are actively investigating the issue.
Notification failures when utilising Outlook (Incident 5087)
Started:
monitoring
A fix has been applied and our engineering teams are actively reviewing our telemetry to confirm this fix has mitigated the issue.
investigating
Customers utilising Outlook may receive delivery notification failures when sending envelopes to signers. Engineering teams have been engaged and we are actively triaiging this issue.
Users may encounter errors when attempting to process envelopes (Incident 5072)
Started:
investigating
We are investigating this issue.
Document Upload and Generation Errors (Incident 5073)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue and a fix is being implemented.
investigating
We continue to investigate the issue.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Customers Unable to Purchase Plans (Incident 5034)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue and a fix is being implemented.
investigating
We are actively investigating this issue.
Organization Reports May Remain in "Exporting" Status (Incident 5020)
Started:
identified
We are continuing to work on a fix for the issue.
identified
Customers may be experiencing issues when attempting to export organization reports. Our engineering teams are engaged and have identified the cause and are working on a fix for this.
Customers dependent on deprecated TLS ciphers will experience interruption (Incident-5003)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
May 2026
Issues utilising +86 country code for sending envelopes and phone authentication (Incident 4968)
Started:
identified
Engineers have identified the root cause and are executing a fix.
identified
Customers attempting to send an envelope or use SMS/Phone Authentication for Envelopes utilising a +86 will experience errors during this process. Engineering teams have been engaged and triage is underway.
Customers may experience timeouts related to core AI features which include document summarization and extractions. (incident 4961)
Started:
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Salesforce is experiencing an outage that may impact customers using the Salesforce integration (Incident-4935)
Started:
investigating
Salesforce is experiencing an outage that may impact customers using the Salesforce integration. Docusign services are not experiencing any outages at this time. The issue will resolve when Salesforce resolves their outage.
Some customers may experience latencies sending and signing in EU (Incident-4915)
Started:
investigating
We are continuing to investigate the issue.
investigating
We are currently investigating the issue.
Some customers may experience latencies sending and signing in NA1 and NA3 (Incident-4902)
Started:
investigating
We are currently investigating this issue.
Users may experience document report failures and loading delays in the EU11 and EU21 sites (incident 4863)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Workflow Reports Experiencing Timeout Errors (Incident 4874)
Started:
monitoring
A fix has been implemented and we are observing telemetry to validate.
identified
We are continuing to work on a fix for this issue.
identified
Customers may be experiencing timeout errors with Workflow and Document Reports. Engineering teams have been engaged and the issue has been identified, a fix is currently being implemented.
Customers may experience issues accessing PowerForms (Incident-4870)
Started:
investigating
We are currently investigating this issue.
Users may experience timeouts when attempting to complete document transactions (incident 4866)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Users may experience connection errors when trying to switch to CLM or utilising DocuSign edit (Incident 4862)
Started:
monitoring
A fix has now been implemented and we are seeing improvements, we will continue monitoring telemetry to ensure the fix is final.
identified
Additional Engineering teams have been engaged to triage this issue, the current workaround is still functional:
To restore access, please contact your IT department or security team and request that the following URL be unblocked/allowed:
https://login.springcm.com
Once this URL has been added to your allowlist, you should be able to log in without any further issues.
Further investigation with our engineering teams is underway to fully resolve this issue.
monitoring
Our engineering teams have deployed a fix and we are now monitoring to validate.
identified
We are continuing to work on a fix for this issue.
identified
We are currently investigating an issue where a subset of customers utilising a particular firewall may experience issues when attempting to switch to CLM.
To restore access, please contact your IT department or security team and request that the following URL be unblocked/allowed:
https://login.springcm.com
Once this URL has been added to your allowlist, you should be able to log in without any further issues.
Further investigation with our engineering teams is underway to fully resolve ...
Users may experience connection errors when trying to switch to CLM (Incident 4861)
Started:
investigating
Additional teams have been engaged to triage this issue.
investigating
A subset of customers may be experiencing connection errors in the UI when attempting to switch to CLM. Engineering teams have been engaged and are actively triaging this issue.
Users may encounter errors that will prevent document uploading or envelope creation (Incident 4860)
Started:
identified
The issue has been identified and a fix is being implemented.
AU Site Outage (Incident 4840)
Started:
monitoring
We have implemented a mitigation and are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue.
April 2026
Send Latency in EU (Incident 4776)
Started:
identified
Engineers have identified a root cause and are working on releasing a fix.
investigating
A subset of customers in EU may experience latency with Send operations. Engineering teams have been engaged and are actively triaging.
Some customers are seeing errors previewing and sending envelopes via Docusign App Launcher (Incident 4752)
Started:
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Some users might experience latency when attempting to convert non-PDF documents (Incident-4750)
Started:
monitoring
We continue to monitor for stability while we investigate possible secondary factors.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We continue to monitor the environment to ensure stability.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Customers may experience intermittent latency and errors in Navigator (Incident 4748)
Started:
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
More engineering teams have been engaged to triage this error and investigation is continuing.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating the issue.
Login failures and Latency Issues with Sending and Signing Envelopes
Started:
monitoring
We are continuing to monitor for any further issues.
monitoring
Internal testing is showing the implemented fix has resolved the impact, we are continuing to monitor to ensure the issue is fully mitigated.
identified
Our engineering teams have identified the root cause of this issue and are in the process of deploying a fix.
investigating
We are currently investigating a spike in latency for send and sign services which may affect a subset of customers. We have engaged our engineering teams and are actively triaging this issue.
Intermittent Errors in UAT (Incident 4682)
Started:
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
Customers may experience intermittent errors, jobs not completing, and the inability to login to UAT.
User Membership Group Update Delays (Incident 4672)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are implementing a change to resolve the AU delay.
identified
NA1 is now back to normal operational expectations. We are working to resolve the issue in AU now.
identified
Changes to user membership groups is significantly delayed. We are making changes to reduce or remove the delay.
March 2026
Issues in UAT and DEMO S1 when attempting to complete tasks in task groups (Incident 4591)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
Engineers are continuing to triage and develop a fix to the identified issue.
identified
A potential cause has been identified, engineering teams are reproducing the issue and reviewing telemetry before applying a fix.
investigating
More engineering teams have been engaged to triage this error and investigation is continuing.
investigating
Due to a recently identified issue in our UAT environments, tasks may be routed incorrectly, leading to failures. Our team is actively working on identifying the root cause and mitigating it, and we will keep you updated as progress is made. Please note that any workflows and tasks on your Production environment should not be affected, and will still be executed normally.
Search Indexing Delays (Incident 4539)
Started:
identified
As a continuation of incident 4517, a subset of customers may experience incomplete search results for historical documents older than one year. A fix is currently underway, and full resolution is anticipated by Wednesday, March 18, 2026 at 11:00 AM UTC.
CLM & Salesforce Integration Customers may be having difficulties accessing EU sites (Incident 4517)
Started:
monitoring
We continue to monitor the environment to ensure stability.
Any company logos that were missing or outdated have been updated.
monitoring
We continue to monitor the environment to ensure stability. Updates will be posted less often during monitoring unless a significant issue develops.
Customers may notice some visual issues, such as custom logos not appearing. Services are functional.
monitoring
A fix has been implemented and we are monitoring the results.
Customers may notice some visual issues, such as custom logos not appearing. Services are functional.
identified
The failover steps for EU21 are nearing completion. A subset of customers have been enabled and we are monitoring carefully.
identified
We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.
identified
We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.
identified
We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.
identified
We are still continuing to work through the failover steps for EU21.
identified
We are still continuing to work through the failover steps for EU21, additional engineering resources have been engaged. EU11 is now full recovered.
identified
We are still continuing to work through the failover steps for EU21. EU11 is now showing signs of recovery and we are continuing to monitor the health of the site to ensure stability.
identified
We are still continuing to work through the failover steps for EU21. Eu11 Remains in a degraded state, additional engineering teams haven been engaged and triage is continuing.
identified
We are still continuing to work through the failover steps for EU21. Engineering teams are still triaging issues on EU11.
identified
We are continuing to work through the failover steps for EU21. We have identified the issue with EU11 and are now working to implement a fix to restore service.
identified
We are continuing to work through the failover steps for EU21. We are now seeing additional impact to our EU11 site and have engaged further engineering resources to triage.
identified
We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.
identified
We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.
identified
We have identified an intermittent degradation in our EU11 environment and are working on fixing it.
identified
We are continuing to work through failover steps.
identified
We are continuing to work through failover steps.
identified
We have identified that the recovery of EU21 will require the failover of our compute systems. This is a complex operation and will take some time. We will provide updates every 2 hours as recovery progresses.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to remediate impact to EU21 customers.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to remediate impact to EU11 and EU21 customers.
identified
We are continuing to work on a fix for EU21 customers. EU21 customers may observe issues accessing the site. EU11 customers may see intermittent issues generating documents.
monitoring
A fix has been implemented for US sites as of approximately 09:00 UTC.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue.
Users may encounter errors while attempting to upload or edit documents. (Incident 4504)
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue. We estimate the fix will be deployed by 22:30 UTC
identified
We are continuing to work on a fix for this issue. We estimate the fix will be deployed by 22:30 UTC
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.