Blogs

Report on our investigation of the 2025-10-20 incident in AWS us-east-1 — PlanetScale

Planetscale

On 2025-10-20, there was an incident that affected PlanetScale, initially caused by DNS misconfiguration in one of PlanetScale’s service providers, followed by several hours of capacity constraints and network instability.

Visit Site

Blogs Planetscale

BlogsComparing AWS’s RDS and PlanetScalePlanetscale BlogsMySQL data types: VARCHAR and CHARPlanetscale BlogsAnnouncing PlanetScale MetalPlanetscale BlogsIdentifying and profiling problematic MySQL queriesPlanetscale BlogsWorking with Geospatial Features in MySQLPlanetscale BlogsDealing with large tablesPlanetscale BlogsHoneycomb + Cloudelligent Bring Observability to AWSHoneycomb BlogsMulti-Agent Collaboration on a Shared CanvasHoneycomb BlogsHoneycomb Announces Availability of MCP in the New AWS Marketplace AI Agents and Tools CategoryHoneycomb BlogsFrom Prototype to Production With AWS AgentCoreHoneycomb BlogsHoneycomb Acquires Grit and Expands Leadership Team to Accelerate Customer Value and EnterpriseHoneycomb BlogsAWS PrivateLink for Neon Databases - NeonNeon BlogsState of AI 2025: How Developers Are Adopting AI Coding Tools - NeonNeon BlogsRethinking Snapshots at Scale: Neon vs AWS RDS - NeonNeon BlogsIs your AWS RDS bill bloated? - NeonNeon BlogsHow to Set Up Nightly Backups to AWS S3 for Multiple Neon Projects - NeonNeon BlogsPrelude To Summer (June 2025 Wallpapers Edition)Smashingmagazine BlogsOctober 21, 2025 Smashing Newsletter: Issue #530Smashingmagazine BlogsDesigning For TV: Principles, Patterns And Practical Guidance (Part 2)Smashingmagazine NewsReport: What's New in ECMAScript and JavaScript for 2020Thenewstack