Measuring uptime for Neon’s multi-tenant architecture

The company behind Neon, a multi-tenant distributed system, has experienced several incidents over the past two months affecting different aspects of their service. They have communicated these incidents through their status page, which provides updates on what happened, the impact size, and actions taken to prevent similar issues in the future. The company removed the uptime percentage metric from their status page due to its inaccuracy, instead exploring a new metric that better represents the health of their system. Neon's architecture separates storage and compute layers, leading to issues such as noisy neighbors causing high IO on compute nodes or internal API requests, which were addressed by implementing mitigation strategies and improving retry logic. The company is also working to reduce the blast radius for misconfigured components by switching them to region-local deployments. With their focus on cloud independence, performance, and developer experience, Neon aims to ensure reliability and scalability as they approach general availability.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.