We have noticed the same exact behaviour.

Hi, I have same problem. Any solution ?

Are you seeing this in demo or production? 

@AmyG We are seeing this in demo. We haven’t tested in production because we don’t want to burn a credit.

in demo

@trungduc74f1  Every PDF page is converted into an image during the signing session. The total count of pages, the number of tabs on each page, and the internet speed all affect how quickly pages load.

Without more information and a more thorough inquiry, it is very difficult to determine what went wrong in this case.I’d suggest opening a case through the Support Center and provide your AccountID, sample Envelope ID, and browser HAR recording.

Thank you!  

We had it in demo also, DocuSign fixed it now working again in Demo. Production was working . Try now see if it’s fixed for you in demo

Thanks @AmyG . The bug has been fixed

It is working now. Thanks

We are experiencing this issue currently; it does not appear to be fixed in all situations

I have the same issue at the moment. 
What was done by DocuSign to fix this? 

I have opened a case and described the issue to DocuSign support, but I have yet to receive a response. I sent steps to reproduce the error at 8:12 PM last night.  If an employee of DocuSign is monitoring community threads, can you please escalate the priority of correcting Case 14334316

As an update, as of this morning, the issue appears to have been corrected for us; I did not receive any information about what the underlying issue was or when a fix was applied. I’ve asked them to close the case.

We are experiencing the same type of issue in demo mode (not able to test in production yet), does the issue seem to be resolved here? Any actions/modification required on the client side?

I have seemingly the same issue. The pages 20 - 25 of 25 page envelope with 5 pdf documents added to the envelope. When scrolling up and down sometimes the code loads it and when i scroll past it it removes the CSS “page-loaded” as you can see in F12

I know this is not the most useful answer as this is not a solution, but we are still experiencing this issue in our stage environment but we were able to confirm that this is not happening in production and have had successful signatures happen in prod.