DevMeter Downtime Update: We Hit Our Neon Compute Hour Limit
A transparent update on the current DevMeter downtime caused by reaching our Neon database compute hour limit, what it affected, and what we are doing next.
DevMeter Downtime Update: We Hit Our Neon Compute Hour Limit
DevMeter is currently experiencing an ongoing downtime issue, and we want to explain clearly what is happening.
Right now, some users may see the extension show **Offline**, stats may fail to refresh, and dashboard data may load slowly or not at all. The direct cause is that we reached the **compute hour limit on Neon**, the database provider we currently use for DevMeter.
The Real Cause
DevMeter depends on Neon for database access. Once our compute hour limit was exhausted, database-backed parts of the product could no longer respond normally. That disrupted the core flow between the extension, the API, and the dashboard.
In practical terms, that means:
This is not caused by a broken extension release on your machine. It is an infrastructure limit on our side, and we are actively working through it.
Why This Has Taken Longer Than Expected
This outage has been harder to resolve because the database sits in the middle of the core product path. DevMeter relies on multiple moving parts working together consistently:
When the database becomes unavailable because of a compute limit, all of these layers are affected at once. Fixes need to be rolled out carefully so we do not introduce data inconsistencies or make recovery worse.
What We’re Doing Right Now
Our current focus is on restoring stability before shipping anything new.
We are treating this as the top priority.
What Users Should Expect
Until the issue is fully resolved, you may continue to see intermittent downtime. That means DevMeter may work normally for a period of time and then briefly fail again while we continue recovery work.
If you are affected, the most common symptoms are:
What You Do Not Need To Do
In most cases, you do not need to reinstall the extension or change your API key. If your DevMeter setup was working before this outage began, this issue is most likely unrelated to your local configuration.
If you want to check your setup anyway, make sure:
Our Commitment
We know DevMeter is most useful when it quietly works in the background. Downtime breaks that trust, and we take that seriously.
We would rather be direct than vague: on April 1, 2026, the service became unstable because we exhausted the compute hour limit on our Neon database. The issue is still ongoing, and we are continuing to work on it until normal reliability is restored.
Thank you for sticking with us while we fix it.
---
**We’ll share another update as soon as service is fully stable again.**