Live / Allopneus / Incident
Allopneus: [ALS-36310] [P1] [Triggered] [Synthetics] Allopneus Mobile parcours critique AVEC montage (HO - HNO)
Allopneus · allopneus.comCritical outageResolved2026-09-18 09:59 UTC
Public — what happened
Summary
Allopneus reported that an automated test simulating a key customer journey on its mobile site, specifically the path that includes booking tyre fitting, was failing. The company flagged the issue as critical, and its alert says the check last failed at 09:59:37 CEST on 18 September 2026, with the incident opened at 08:10 UTC that day. Allopneus did not name a cause; its monitoring team asked for a quick look into where the error was coming from. The status is still listed as investigating, although the record also shows a resolution time of 12:14.
Timeline
- Started — 2026-09-18 08:10 UTC
- Resolved — 2026-09-18 12:14 UTC · 4h 04m 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 39, 2026, our weekly internet health report.