ReadingEggs experienced a major incident on July 24, 2026 affecting ReadingEggs and Reading Eggspress and 1 more component, lasting 29m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 24, 2026, 11:06 AM UTC
We are investigating connectivity issues with our CDN and Cloud provider. All products are currently experiencing degradation or unavailability
- monitoring Jul 24, 2026, 11:15 AM UTC
Connectivity appears to have stabilised. We are monitoring for full recovery and continuing to investigate the root cause with our vendors.
- resolved Jul 24, 2026, 11:35 AM UTC
All systems are back to full operation.
- postmortem Jul 24, 2026, 12:49 PM UTC
**Service Disruption — July 24, 2026** **Status**: Resolved **Summary** Between approximately 10:55 and 11:15 UTC, users across our core products \(Reading Eggs, Mathseeds, Fast Phonics, Wordflyers, Reading Eggspress, and related services\) experienced intermittent errors and slow or failed page loads. The issue has been fully resolved and all services have returned to normal operation. **Impact** Affected users may have seen connection timeouts, slow responses, or error pages when accessing our applications. Impact was global and does not appear to have been isolated to any single region or network. **Root Cause** The disruption coincides with an operational issue reported by AWS affecting multiple services in our primary hosting region \(Oregon, US\). This caused backend application servers across several of our services to become temporarily unresponsive, which in turn caused our CDN \(Cloudflare\) to be unable to reach our origin servers — resulting in the errors users experienced. Cloudflare's own network was operating normally throughout; the issue was upstream, at the infrastructure layer. **Timeline \(UTC\)** 10:55 — Elevated error rates begin across multiple services 11:00–11:10 — Peak impact; automated monitoring alerts triggered 11:05–11:15 — Services progressively recover as backend capacity is restored 11:15 — All services confirmed operating normally **Resolution** Affected services recovered automatically as underlying infrastructure capacity was restored. No customer data was affected at any point during this incident. We apologise for the disruption and thank you for your patience.