Skip to main content
Lago logo

Is Lago Down?

No — Lago is up
Lago's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 117 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

Operational
Lago's components, as its status page reports them
ComponentStatus
APIOperational
Current Usage APIOperational
Event Ingestion APIOperational
Dashboard (Lago UI)Operational
APIOperational
Current Usage APIOperational
Event Ingestion APIOperational
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

Reachable
Regions up
8 of 8
Response
117 ms
Checked

By region

  • Amsterdam reachable, 82 ms
  • Chicago reachable, 47 ms
  • Paris reachable, 72 ms
  • San Jose reachable, 94 ms
  • Singapore reachable, 320 ms
  • Stockholm reachable, 63 ms
  • Sydney reachable, 153 ms
  • Toronto reachable, 105 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam22 ms6 ms10 ms55 ms
Chicago28 ms1 ms5 ms40 ms
Paris52 ms1 ms6 ms65 ms
San Jose69 ms2 ms7 ms85 ms
Singapore297 ms4 ms5 ms312 ms
Stockholm39 ms1 ms9 ms55 ms
Sydney124 ms1 ms8 ms146 ms
Toronto44 ms8 ms13 ms78 ms
We check that getlago.com loads, not every feature behind it. Test it yourself

History

Incidents Lago reported

Since Oct 22, 28 days · from status.getlago.com

Incidents
1
Major or critical
0
Median to resolve
6m
  1. 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
195ms

Last 30 days

30-day clean streak
Oct 20: 100.00% uptime, 16 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Nov 6: 100.00% uptime, 32 checks
Nov 7: 100.00% uptime, 32 checks
Nov 8: 100.00% uptime, 32 checks
Nov 9: 100.00% uptime, 32 checks
Nov 10: 100.00% uptime, 32 checks
Nov 11: 100.00% uptime, 32 checks
Nov 12: 100.00% uptime, 32 checks
Nov 13: 100.00% uptime, 32 checks
Nov 14: 100.00% uptime, 32 checks
Nov 15: 100.00% uptime, 32 checks
Nov 16: 100.00% uptime, 32 checks
Nov 17: 100.00% uptime, 32 checks
Nov 18: 100.00% uptime, 8 checks
Oct 20 Today
No downtime Partial Downtime Not measurable No data

Measured 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 — 30 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.

Test it yourself

Related services

Lago outage FAQ

Will retrying events during a Lago outage bill my customers twice?
Not if you resend the identical payload. Lago deduplicates events by transaction_id, across REST, Kafka and S3. On the ClickHouse event store the timestamp is part of the key, and Lago fills a missing timestamp with the ingestion time, so a retry of an event sent without one is billed as a new event. Lago says retrying after a 429 is safe, and to investigate a 5xx before retrying.
Does a Lago Cloud outage affect self-hosted Lago?
The status page does not cover self-hosted instances. Lago's documentation describes it as the managed service's status, and its components are the Lago Cloud US and EU clusters. A self-hosted deployment runs on your own infrastructure, where your team operates the application, its databases, upgrades and monitoring, so its health has to be checked on your side.
Which Lago region am I on, and how long do incidents last?
Your organization lives in one region: the US API is api.getlago.com/api/v1 and the EU API is api.eu.getlago.com/api/v1, and SDKs default to the US. Of the ten incidents in the 90 days to October 20, 2026, seven hit the EU cluster's API and three the US cluster's. Most were resolved within 30 minutes; the longest, on September 11, 2026, lasted about three and a half hours.
Will Lago resend webhooks my server missed?
Yes, a limited number of times. Lago makes up to 3 delivery attempts per event, the first call plus 2 retries, and marks any response other than 200, 201, 202 or 204 as failed. Failed events show in the webhook logs under Developers, then Webhooks, where you can retry them. Self-hosted instances set the attempts with LAGO_WEBHOOK_ATTEMPTS and the timeout with LAGO_WEBHOOK_TIMEOUT_SECONDS, 30 seconds by default.
Does the check above measure the Lago API?
No. It loads getlago.com, Lago's website, not the API at api.getlago.com or api.eu.getlago.com, and not the dashboard. The status page reports those per cluster, and most Lago incidents have been API latency in a single region, so a healthy website does not prove that event ingestion or invoicing in your region is working.

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 403 or 429 means 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
Free plan available No credit card required