3P Learning Outage History
6 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded 3P Learning Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 25, 2026 | Database MaintinenaceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Aug 19, 2026 | Degraded performance affecting readingeggs student applicationThis incident has been resolved. | 12h 10m | Resolved |
| Jul 24, 2026 | Intermittent Connectivity Issue**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… | 29 min | Resolved |
| Mar 1, 2026 | Student apps unavailableThis incident is now resolved | 42 min | Resolved |
| Dec 5, 2025 | Outages across our platformOur sites appear to be fully recovered and operational. | 54 min | Resolved |
| Nov 18, 2025 | Network issues with service providerThis incident has been resolved. | 8h 24m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next 3P Learning incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This 3P Learning Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before 3P Learning acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single 3P Learning outage in this window ran 12h 10m, against a mean recovery of 4h 7m. If you depend on 3P Learning in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.