Live / Allopneus / Incident
Allopneus: [ALS-37130] Flux Michelin Hermes coupé
Allopneus · allopneus.comCritical outageResolved2026-10-27 07:41 UTC
Public — what happened
Summary
Allopneus reported a critical incident titled as a cut in the Michelin Hermes feed, which it said caused delayed customer orders and affected a large share of customers and staff. The company logged the incident at 08:06 UTC on 26 October 2026 and gave 08:30 as the start time, and shortly afterward said its own service was active. Later that day it noted that some items were inactive and said the problem would be resolved the next morning at 8am. Allopneus marked the incident resolved at 07:41 UTC on 27 October, and it did not state a cause in the text provided.
Affected
Impact clients boutiques
Timeline
- Started — 2026-10-26 08:06 UTC
- Investigating — 2026-10-26 08:06 UTC (4 updates)
- Resolved — 2026-10-27 07:41 UTC · 23h 35m 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 45, 2026, our weekly internet health report.