Summary

On Monday, June 23, 2025, customers may have experienced intermittent periods of degraded performance. This disruption was attributed to the exhaustion of specific IP address ranges within our private Amazon Web Services (AWS) networks. This was promptly detected, and our engineering teams swiftly initiated remediation efforts. The issue was identified and resolved within a short timeframe, restoring full service functionality and optimal performance levels.

Customer Impact:

• Incident Duration: 23 Jun 2025, 11:06- 23 Jun 11:33 (AEST) 
• Impact: We have noticed that only a small number of clients have been affected by this incident.

Issue, Resolution, and Mitigation

Root cause Analysis

The underlying cause of this incident was the unanticipated depletion of available IP addresses within designated private subnets in our AWS environment. A confluence of factors, including a surge in specific resource utilization and the rapid provisioning of new instances, led to a temporary bottleneck in IP availability. 

‌

Resolution Actions

1. Identification:

• Squiz Support Teams proactively identified errors relating to this issue

2. Action:

• Releasing recently provisioned IP addresses

Follow-up Actions

1. Squiz Actions:

• To prevent future occurrences, Squiz has completed the migration of specific infrastructure to a larger subnet.