Lingvanex Outage History

9 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Lingvanex status99.83% uptime history

Every Recorded Lingvanex Incident

Lingvanex incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 15, 2026Cloud API is down501h 51mResolved
Oct 14, 2026Cloud API is down521h 28mResolved
Oct 9, 2026Cloud API is down644h 54mResolved
Sep 10, 2026Cloud API is down1334h 31mResolved
Aug 31, 2026Cloud API is down1473h 46mResolved
Jul 12, 2026Cloud API is down1939h 52mResolved
Jul 11, 2026Cloud API is down1959h 39mResolved
Jul 9, 2026Cloud API is down1993h 33mResolved
Jun 15, 2026Cloud API is down1854h 36mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Lingvanex incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Lingvanex Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Lingvanex acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Lingvanex outage in this window ran 83d 1h, against a mean recovery of 56d 14h. If you depend on Lingvanex in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.