Skip to main content
25-Diamond I
December 1, 2018
Question

12/1 Weekend Maintenance

  • December 1, 2018
  • 5 replies
  • 9989 views

Problem seemed to be solved for a while but quite now it again took minutes to log in

5 replies

Werner_E25-Diamond IAuthor
25-Diamond I
December 2, 2018

Again! Problem not solved!

I was just about to cancel the process when finally after some minutes the login was successful.

It looked to me as if support.ptc.com was the problem and not lithium, but I may be wrong about that.

Werner_E25-Diamond IAuthor
25-Diamond I
December 2, 2018

In case anybody cares - just now it took me 3 minutes and 20 seconds for being back to the community page after entering my login data at support.ptc

Problem not solved 😞

23-Emerald III
December 3, 2018
I am also seeing the problem again. I tried both Mozilla Firefox and IE 11. This reply was done via email and just as I was finishing, the login was successful on both.
21-Topaz II
December 3, 2018

To echo others comments, it took over 2 minutes this morning from submitting my credentials to seeing the page I was headed to (private messages).

23-Emerald IV
December 3, 2018

I just logged in.  Took me 2 minutes and 15 seconds.

Dale_Rosema
23-Emerald III
23-Emerald III
December 3, 2018

There was some sort of maintenance done over the weekend. Did that get done correctly?

 

https://community.ptc.com/t5/PTC-Community-Announcements/PTC-Community-Read-Only-State-December-1st-between-08-30-and-19/m-p/583189#M47

23-Emerald IV
December 4, 2018

@Jaime_Lee, login today - 2 minutes and 8 seconds.

Community Manager
December 4, 2018

Thank you all for your feedback.  A ticket is open with the internal PTC IT team to research this!  

Stay tuned to this thread for updates.

23-Emerald IV
December 4, 2018

Like Doug said, they're one in the same.  Normally I log into the community first so I'm automatically logged into support as well.  Doing some more testing, the delay is the same.  It doesn't matter if I start from the community or I start at support, the delay is identical.  I've also confirmed that the delay is not browser specific.  I can reproduce it with Chrome, Firefox, and Edge.