Major incident
Pylon: [EU-hosted instances] Platform Loading Issues/Unable to Login
Oct 12, 2026, 12:28 UTC
started
12:51 UTC
resolved
23 min
duration
Current status of Pylon: Operational — live Pylon status
Timeline
- Oct 12, 2026, 12:28 UTCinvestigatingWe’re investigating reports that users are unable to log in to Pylon and are seeing a “Something went wrong” error. This is affecting customers on EU-hosted Pylon instances. Instances hosted in other regions are not affected at this time. Our team is actively working to identify the cause, and we’ll share another update within 30 minutes or sooner as we learn more. We apologize for the disruption.
- Oct 12, 2026, 12:36 UTCmonitoringWe have implemented a fix and are monitoring our systems.
- Oct 12, 2026, 12:51 UTCresolvedThe issue has been resolved and all systems are operational.
Updates as published by Pylon.
Other services with incidents at the same time
- WiscNet 13:26 UTC · [2302651] Woodruff J1 School District - 400674 - Down
- Sage 13:12 UTC · AutoEntry - Core
- Cloudflare 12:54 UTC · Network Performance Issues in Seattle
- gva 12:50 UTC · [GVA] PaaS Panel Unavailable
- FlippingBook 12:32 UTC · Problem with logging into FlippingBook Publisher
- GitHub 12:21 UTC · Incident with Actions, Pull Requests and Issues
- Twilio 11:53 UTC · Voice Call Post Dial Delay From a Subset of Twilio Phone Numbers to Thailand
- Klarna 11:45 UTC · BankID sign-in degradation in Norway
- InterServer 11:33 UTC · Kvm443 cpu replacement
More Pylon incidents
- October 14, 2026 Platform loading issues
- October 6, 2026 Platform loading issues and events processing delay
- October 1, 2026 Errors when sending SMS and receiving phone calls
- September 28, 2026 Inbound Email Delays for US Hosted Workspaces
- September 9, 2026 Latency Issues within the Pylon Platform
- August 17, 2026 Codebase search failures