M1 Outage History

M1 is up right now

M1 had 6 outages in the last 2 years totaling 34h 59m of downtime — averaging 0.2 incidents per month.

There were 6 M1 outages since October 20, 2025 totaling 34h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.m1.com

Major June 22, 2026

Login issues

Detected by Pingoru
Jun 22, 2026, 02:09 PM UTC
Resolved
Jun 22, 2026, 08:27 PM UTC
Duration
6h 18m
Affected: Dashboard
Timeline · 3 updates
  1. investigating Jun 22, 2026, 02:09 PM UTC

    Some clients are experiencing login issues. We’re working to restore services as soon as possible. We’re sorry for the inconvenience and appreciate your patience.

  2. identified Jun 22, 2026, 02:32 PM UTC

    The issue has been identified with an upstream system and a fix is being implemented. Service has been partially restored and our team continues to monitor the situation.

  3. resolved Jun 22, 2026, 08:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 10, 2026

Android Login Issues

Detected by Pingoru
Jun 10, 2026, 01:12 PM UTC
Resolved
Jun 11, 2026, 02:23 PM UTC
Duration
1d 1h
Affected: Dashboard
Timeline · 3 updates
  1. investigating Jun 10, 2026, 01:12 PM UTC

    Some clients are experiencing login issues. We’re working to restore services as soon as possible. We’re sorry for the inconvenience and appreciate your patience. Please check our status for updates: https://status.m1finance.com/

  2. investigating Jun 10, 2026, 08:05 PM UTC

    We are continuing to investigate this issue.

  3. resolved Jun 11, 2026, 02:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 9, 2026

Client Center outage

Detected by Pingoru
Jan 09, 2026, 08:29 PM UTC
Resolved
Jan 09, 2026, 09:24 PM UTC
Duration
54m
Affected: Help Center
Timeline · 3 updates
  1. investigating Jan 09, 2026, 08:29 PM UTC

    Our support tool Intercom has identified an issue causing slowness and errors within our Client Messenger tool. They are currently investigating the problem and working on a solution. In the meantime, please email [email protected].

  2. investigating Jan 09, 2026, 09:21 PM UTC

    This incident has been resolved.

  3. resolved Jan 09, 2026, 09:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 16, 2025

Login Issues

Detected by Pingoru
Nov 16, 2025, 08:09 PM UTC
Resolved
Nov 16, 2025, 09:05 PM UTC
Duration
56m
Affected: Dashboard
Timeline · 2 updates
  1. investigating Nov 16, 2025, 08:09 PM UTC

    Some clients are experiencing login issues. We’re working to restore services as soon as possible. We’re sorry for the inconvenience and appreciate your patience.

  2. resolved Nov 16, 2025, 09:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 29, 2025

Statements availability issues

Detected by Pingoru
Oct 29, 2025, 12:57 AM UTC
Resolved
Oct 29, 2025, 02:16 AM UTC
Duration
1h 19m
Affected: Statements & Confirms
Timeline · 2 updates
  1. investigating Oct 29, 2025, 12:57 AM UTC

    We are currently investigating an issue affecting customer statements. Some users may experience difficulty accessing statements at this time. Our team is actively working to identify the cause and restore full functionality. We apologize for any inconvenience this may cause.

  2. resolved Oct 29, 2025, 02:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2025

Trade windows are delayed

Detected by Pingoru
Oct 20, 2025, 07:42 PM UTC
Resolved
Oct 20, 2025, 08:02 PM UTC
Duration
20m
Affected: Trading
Timeline · 2 updates
  1. identified Oct 20, 2025, 07:42 PM UTC

    We are currently experiencing delays with our trade window. Our team has identified the issue and we are working to get today’s trades back on track. Thank you for your patience. We will provide another update when trades resume.

  2. resolved Oct 20, 2025, 08:02 PM UTC

    This incident has been resolved.

Read the full incident report →