Magic Labs Outage History

Magic Labs is up right now

Magic Labs had 4 outages in the last 2 years totaling 2h 10m of downtime — averaging 0.2 incidents per month.

There were 4 Magic Labs outages since August 27, 2025 totaling 2h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.magic.link

Critical June 3, 2026

Service Interruption

Detected by Pingoru
Jun 03, 2026, 05:51 PM UTC
Resolved
Jun 03, 2026, 06:34 PM UTC
Duration
42m
Affected: AuthenticationAPIWallet Operations
Timeline · 2 updates
  1. investigating Jun 03, 2026, 06:12 PM UTC

    We are currently investigating this issue.

  2. resolved Jun 03, 2026, 06:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 18, 2026

Partial Degraded Experience

Detected by Pingoru
Feb 18, 2026, 07:15 AM UTC
Resolved
Feb 18, 2026, 07:52 AM UTC
Duration
36m
Affected: Wallet Operations
Timeline · 3 updates
  1. investigating Feb 18, 2026, 07:15 AM UTC

    We are currently investigating this issue.

  2. monitoring Feb 18, 2026, 07:50 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 18, 2026, 07:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 9, 2026

Issues with Signing

Detected by Pingoru
Feb 09, 2026, 07:29 PM UTC
Resolved
Feb 09, 2026, 08:05 PM UTC
Duration
35m
Affected: Wallet Operations
Timeline · 3 updates
  1. identified Feb 09, 2026, 07:29 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Feb 09, 2026, 07:37 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 09, 2026, 08:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 13, 2026

Elevated timeouts in Signing service

Detected by Pingoru
Jan 13, 2026, 08:01 PM UTC
Resolved
Jan 13, 2026, 08:17 PM UTC
Duration
15m
Timeline · 2 updates
  1. identified Jan 13, 2026, 09:23 PM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved Jan 13, 2026, 09:24 PM UTC

    This incident has been resolved.

Read the full incident report →