Other customers reported this error back in June, and it's persisted now for several months. Per the alert in the link below, those of us impacted last received an update a full month ago.
Can we please get a further update on this alert, even just to confirm the issue is still being actively investigated? Is this still in progress somewhere, and is it actually being looked at by a technical resource or negotiated with Human Interest?