Live / Laposta / Incident
Laposta: Vertraging bij verwerking events
Laposta · laposta.nlMinor incidentResolved2026-11-10 13:30 UTC
Public — what happened
Summary
Laposta reported a minor delay in handling events, which covers the processing of statistics and sign-ups, and said these were arriving about 15 minutes late. The company said the cause was heavier than usual traffic, which created a queue. Its first update came at 12:38 UTC, and at 13:13 UTC it said it was still working on a fix with nothing new to share. The incident was marked resolved at 13:30 UTC.
Affected
Resultaten, Aanmeldformulieren, API en koppelingen
Timeline
- Started — 2026-11-10 12:36 UTC
- Investigating — 2026-11-10 12:38 UTC
- Identified — 2026-11-10 12:40 UTC (2 updates)
- Resolved — 2026-11-10 13:30 UTC · 54 min 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 47, 2026, our weekly internet health report.