- Service Status
- /
- Lago

Is Lago Down?
- Lago's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 136 ms
Right now
The verdict is the worse of these two. How we decide
Lago's status page
status.getlago.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| API | Operational |
| Current Usage API | Operational |
| Event Ingestion API | Operational |
| Dashboard (Lago UI) | Operational |
| API | Operational |
| Current Usage API | Operational |
| Event Ingestion API | Operational |
| Dashboard (Lago UI) | Operational |
FlareWarden checks
getlago.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 136 ms
- Checked
By region
- Amsterdam reachable, 71 ms
- Dallas reachable, 88 ms
- Paris reachable, 49 ms
- San Jose reachable, 187 ms
- Singapore reachable, 203 ms
- Stockholm reachable, 95 ms
- Sydney reachable, 219 ms
- Toronto reachable, 182 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 36 ms | 3 ms | 8 ms | 61 ms |
| Dallas | 67 ms | 2 ms | 6 ms | 81 ms |
| Paris | 27 ms | 1 ms | 6 ms | 43 ms |
| San Jose | 166 ms | 1 ms | 6 ms | 179 ms |
| Singapore | 179 ms | 2 ms | 6 ms | 193 ms |
| Stockholm | 38 ms | 4 ms | 9 ms | 82 ms |
| Sydney | 109 ms | 15 ms | 18 ms | 165 ms |
| Toronto | 118 ms | 7 ms | 12 ms | 150 ms |
History
Incidents Lago reported
Since Oct 22, 32 days · from status.getlago.com
- Incidents
- 1
- Major or critical
- 0
- Median to resolve
- 6m
- lasted 6m
Lago website availability
Measured by FlareWarden · getlago.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 181ms
Last 30 days
34-day clean streakMeasured by FlareWarden's own checks of getlago.com from multiple regions every 6 hours. Lago's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 34 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Lago does
Lago is an open-source billing platform for usage-based, subscription and hybrid pricing. Applications send usage events to its API, and Lago deduplicates them, matches them to customer subscriptions and pricing plans, and generates invoices, triggering collection through a connected payment provider. Teams use Lago Cloud, a managed service hosted in a US or EU region, or self-host the AGPL-3.0 open-source edition or the Premium edition.
What an outage looks like
Calls to api.getlago.com or api.eu.getlago.com slow down or fail, and usage events take longer to process. Most Lago incidents are higher API latency in one region. On May 11, 2026 a long-running autovacuum on the EU database raised latency, caused failed requests and delayed background jobs and billing, and the incident stayed open from about 07:10 to 14:10 UTC while a backlog of billing events cleared.
What to do about it
Check status.getlago.com under your organization's cluster: US and EU each list API, Current Usage API, Event Ingestion API and Dashboard (Lago UI). Keep events flowing, and when a request fails resend the identical payload, with its original transaction_id and an explicit timestamp, so Lago deduplicates it instead of billing it twice. After the May 2026 backlog, Lago said all events and invoices would be processed once it cleared.
Is it down for everyone, or just you?
If this page says Lago is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Lago outage FAQ
Will retrying events during a Lago outage bill my customers twice?
Does a Lago Cloud outage affect self-hosted Lago?
Which Lago region am I on, and how long do incidents last?
Will Lago resend webhooks my server missed?
Does the check above measure the Lago API?
How we measure this
- We request Lago's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Lago publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Lago itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Lago goes down
We check Lago every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring

