Live / Laposta / Incident
Laposta: Inloggen en applicatie zijn niet bereikbaar
Laposta · laposta.nlCritical outageResolved2026-11-04 12:09 UTC
Public — what happened
Summary
Laposta reported a critical incident in which its login page and application could not be reached, beginning at 10:44 UTC on 2026-11-04. The company said one of its underlying servers had briefly gone offline and was restored right away, and it then kept watching to make sure things stayed stable. Laposta said at 11:34 UTC that the service was fully working again, while it was still looking into the source of the disruption. The incident is marked resolved as of 12:09 UTC.
Affected
Inloggen, Applicatie, Beheeromgeving
Timeline
- Started — 2026-11-04 10:44 UTC
- Investigating — 2026-11-04 10:46 UTC
- Monitoring — 2026-11-04 10:51 UTC (2 updates)
- Resolved — 2026-11-04 12:09 UTC · 1h 25m 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 46, 2026, our weekly internet health report.