Post-mortem on 19 May 2026 outage
On the night of 19–20 May, around 200 Magic Pages sites went offline for about four and a half hours. I want to be upfront
Announcing the Magic Pages Open House. Quarterly calls with our team!
On the night of 19–20 May, around 200 Magic Pages sites went offline for about four and a half hours. I want to be upfront
Today, on 29 January 2026, from approximately 13:30 UTC to around 22:45 UTC, Magic Pages experienced an extended outage affecting customer websites. This was
<|endoftext|>How to remove the "Continue with Google" button in NextAuth.js
Magic Pages faced an ActivityPub federation issue from June 20–21, 2025, due to endpoint misconfigurations after a code update; the problem was traced to.
April 2025, a Kubernetes control plane failure triggered a Magic Pages outage; limited API visibility delayed recovery until redundant systems stabilized.
A misconfigured Ansible update and an outdated static IP address caused a 16-minute outage across all Magic Pages customer sites on 19/20 March 2025.
Magic Pages had a 100-minute database outage caused by Kubernetes storage issues during node recovery. Here's our technical breakdown.
Magic Pages sites showed 502 errors on Oct 22 due to a Bunny.net routing issue. Service restored in 15 minutes after their fix.
Magic Pages experienced a 35-minute outage when a network switch failure prevented failover systems from working as designed.
Magic Pages experienced a 70-minute outage on June 19 after switching DNS providers. Here's what broke, why it happened, and the fix.
We'll send you a monthly round-up of new features at Magic Pages, Ghost CMS updates, helpful tutorials, and exclusive tips we've learned from working with 1,400+ publishers.