Live / Laposta / Incident
Laposta: Systemen uit voorzorg uitgeschakeld door wereldwijde kwetsbaarheid in PHP
Laposta · laposta.nlMajor incidentResolved2026-10-21 15:58 UTC
Public — what happened
Summary
Laposta said it switched off its systems as a precaution on 21 October 2026 at 11:20 UTC, citing a worldwide security weakness in PHP, the programming language it uses. The company said scheduled campaigns and automations would be sent later, and that sign-up, unsubscribe and update forms, plus links and images in already-sent campaigns, might not work. Laposta said a security update was expected around 16:00 Dutch time and that it would install it and check all its systems before turning the service back on. The incident was marked resolved at 15:58 UTC.
Affected
Website, Applicatie, Campagnes versturen, Statistieken, Automation, API
Timeline
- Started — 2026-10-21 11:20 UTC
- Identified — 2026-10-21 11:20 UTC
- Monitoring — 2026-10-21 12:57 UTC
- Resolved — 2026-10-21 15:58 UTC · 4h 38m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Laposta against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Laposta: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Laposta report →
More from Laposta
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.