Multilogin Outage History

29 incidents recorded over the last 365 days, 29 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 Multilogin status99.31% uptime history

Every Recorded Multilogin Incident

Multilogin incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 5, 2026Releasing new features1h 0mResolved
Oct 31, 2026Mobile profile is down119h 15mResolved
Oct 28, 2026Mobile profile is down175h 40mResolved
Oct 20, 2026Releasing new features3h 0mResolved
Oct 16, 2026Mobile profile is down473h 25mResolved
Oct 13, 2026Mobile profile is down556h 3mResolved
Oct 8, 2026Authentication is down667h 13mResolved
Oct 8, 2026Releasing new features2h 0mResolved
Oct 6, 2026Releasing new features3h 0mResolved
Sep 29, 2026Mobile profile is down887h 24mResolved
Sep 24, 2026Releasing new features1h 0mResolved
Sep 23, 2026Releasing new features2h 0mResolved
Sep 22, 2026Releasing new features2h 0mResolved
Sep 12, 2026Multilogin Proxy is down1283h 9mResolved
Sep 8, 2026Scheduled maintenance on MLX UI1h 0mResolved
Sep 8, 2026Releasing new features2h 59mResolved
Sep 3, 2026Upgrade Android 10 on mobile profiles2h 0mResolved
Aug 25, 2026Scheduled maintenance - CORE backend release1h 0mResolved
Aug 12, 2026MLX prod maintenance1h 0mResolved
Aug 11, 2026MLX prod maintenance1h 30mResolved
Aug 8, 2026Proxy Service Issue2019h 57mResolved
Aug 7, 2026Proxy Service Issues2044h 52mResolved
Jul 29, 2026Intermittent issues with Mobile Profiles990h 22mResolved
Jul 29, 2026Intermittent issues with Mobile Profiles1530h 41mResolved
Jul 28, 2026MLX prod maintenance30 minResolved
Jul 16, 2026MLX prod maintenance1h 3mResolved
Jul 8, 2026Proxy service is down2034h 29mResolved
Jun 30, 2026MLX prod maintenance2h 0mResolved
Jun 9, 2026MLX prod maintenance - Hot Fix1h 21mResolved

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 Multilogin 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 Multilogin 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 Multilogin 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 Multilogin outage in this window ran 85d 4h, against a mean recovery of 18d 9h. If you depend on Multilogin 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.