Live  /  Allopneus  /  Incident

Allopneus: [ALS-37563] Cousin mieux disant non identifié

Allopneus · allopneus.comCritical outageResolved2026-11-10 11:16 UTC
Public — what happened

Summary

Allopneus reported a new incident, which it rated critical and labeled as an unidentified lower-price competitor issue, and said it was investigating. The company said customers were affected by corrupted catalogue and pricing information on its website, and described the impact as significant, reaching a large share of customers and staff. It gave the start of the incident as 12:15 on 10 November 2026, with the first status entry posted at 11:16 UTC. No cause had been named and the incident was not marked as resolved.

Affected

Impact clients boutiques

As listed on Allopneus’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 47, 2026, our weekly internet health report.

The full archive is on the Allopneus status & history page.

Related: Allopneus status & history. SquidGrid is not affiliated with Allopneus.