Live / Shoptet / Incident
Shoptet: Degraded performance of ... / Partial unavailability of ... / Unavailability of ... | Omezený výkon ... / Částečná nedostupnost ... / Nedostupnost ... | Obmedze
Shoptet · shoptet.czMajor incidentResolved2026-10-02 17:22 UTC
Public — what happened
Summary
Shoptet posted a major incident on its status page on 2 October 2026 at 16:46 UTC, using a template title covering degraded performance or full or partial unavailability without naming the affected service or saying which customers were hit. The company first said it was looking into the problem, and by 16:54 UTC reported that a fix was in place, the affected parts were working normally again, and it was keeping watch. At 17:07 UTC it posted that it had found the cause and was working on a resolution, though it did not describe that cause. The incident was marked resolved at 17:22 UTC.
Timeline
- Started — 2026-10-02 16:46 UTC
- Identified — 2026-10-02 16:46 UTC
- Monitoring — 2026-10-02 16:54 UTC (2 updates)
- Identified — 2026-10-02 17:07 UTC
- Resolved — 2026-10-02 17:22 UTC · 36 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 Shoptet 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 Shoptet: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Shoptet report →
More from Shoptet
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.