We identified an issue in our traffic protection layer that caused some unauthenticated Customer Portal requests to be grouped together incorrectly. As a result, rate limiting was applied more aggressively than intended, preventing some users from accessing the service.
Posted Jun 15, 2026 - 23:32 UTC
Identified
The issue has been identified as a WAF (firewall) rule meant to protect against denial of service. The service is back online, and we continue to investigate the cause of the traffic spike.
Posted Jun 15, 2026 - 22:53 UTC
Investigating
We are investigating a spike in API errors that are preventing the Customer Portal from loading.