Live / amazee.io / Incident
amazee.io: Notice: Webhook Signature Verification
amazee.io · amazee.ioinvestigating2026-11-02 23:16 UTC
Public — what happened
Summary
amazee.io posted a notice, listed with no severity rating, saying its Lagoon platform is now requiring signature checks on all incoming webhooks so that only verified requests from a Git provider can trigger automatic actions. The company said automatic actions started by Git webhooks will stay paused for a repository until a webhook token secret is set up. It said live environments, scheduled jobs, backups and site data are not affected and that manual deployments through the Lagoon UI and command-line tool still work. The notice began at 23:16 UTC on 2026-11-02, remains marked as investigating, and directs customers to an amazee.io page for update instructions.
Timeline
- Started — 2026-11-02 23:16 UTC
- Investigating — 2026-11-02 23:16 UTC
- Ongoing at last check.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach amazee.io 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 amazee.io: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the amazee.io report →
More from amazee.io
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.