Sean's note points to an MTU issue -- it's unusual for residential broadband networks to have an MTU size larger than 1500 bytes. It sounds like Verizon's routers are not fragmenting packets when necessary.
If the issue is lack of proper packet fragmentation, SDCCU could help their customers by clamping down their MTU to 1500 (either on the server hosting the website or load balancer or router(s)). I'm assuming, of course, that Verizon's FiOS subscribers use home routers that already have a maximum MTU of 1500, but if they don't, many routers can be manually set to that size.
Any idea what it was they did to fix it? I've still got a ton of customers that are not working. Were you static or DHCP? Did the fix happen due to getting a new IP lease?
@JamesLaszko all we were told is that they were aware of the issue, that it was affecting many others in SoCal and were working on it. My internet did go up and down as they were working on it. I have a dynamic IP and they did not ask me to do anything on my end. I'm not sure if they fixed the widespread issue, or just addressing it per user as each calls in.
@shayne571: OK - we have been working with the VZ IP NOC and they were oblivious to the issue and had not actually been presented with any chronic / trended / known issue type of escalations, so I'm curious what is being done to correct the issue. Will continue the march! Thanks.
Experienced same connection issue with my FiOS service at Rhode Island location. My connection issue resolved by completing system restore to the restore point prior to Windows Update KB2585542 installation.
Here is another report of Windows update KB2585542 causing connection issues. This SSL connection issue should not be assumed as limited to southern CA. As I previously noted, my ability to connect with SSL sites was restored once I removed Microsoft update KB2585542 by a system restore. Both my XP & Win7 using IE9 had SSL connections issues that were resolved upon removing KB2585542.