Live / Allopneus / Incident
Allopneus: [ALS-36758] [P1] [Triggered] [Synthetics] Allopneus Mobile parcours critique AVEC montage (HO - HNO)
Allopneus · allopneus.comMajor incidentResolved2026-10-08 10:38 UTC
Public — what happened
Summary
Allopneus reported a major incident on its status page affecting a key step of its mobile site, the purchase journey that includes tyre fitting, after an automated check flagged a problem on 2026-10-08 at 09:48 UTC. The company said it began looking into the issue right away, and by 09:54 UTC it reported that a fix was in place and it was watching the results. Allopneus did not share a cause, and it marked the incident resolved at 10:38.
Affected
Impact clients boutiques
Timeline
- Started — 2026-10-08 09:48 UTC
- Investigating — 2026-10-08 09:48 UTC
- Monitoring — 2026-10-08 09:54 UTC
- Resolved — 2026-10-08 10:38 UTC · 51 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 Allopneus 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 Allopneus: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Allopneus report →
More from Allopneus
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.