Matlantis Outage History

Matlantis is up right now

Matlantis had 5 outages in the last 2 years totaling 22h 30m of downtime — averaging 0.2 incidents per month.

There were 5 Matlantis outages since March 3, 2025 totaling 22h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.matlantis.com

Minor August 27, 2026

[Incident] Some structure files (xyz, cif, etc.) cannot be opened in Notebook

Detected by Pingoru
Aug 27, 2026, 08:42 AM UTC
Resolved
Aug 27, 2026, 10:32 AM UTC
Duration
1h 50m
Affected: Matlantis (Japan)Matlantis (US)Matlantis (EU)
Timeline · 4 updates
  1. investigating Aug 27, 2026, 09:07 AM UTC

    We are currently investigating this issue.

  2. identified Aug 27, 2026, 09:12 AM UTC

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

  3. monitoring Aug 27, 2026, 10:29 AM UTC

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

  4. resolved Aug 27, 2026, 10:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 12, 2025

[Incident] Group Drive usage is less than actual

Detected by Pingoru
Dec 12, 2025, 06:32 AM UTC
Resolved
Dec 12, 2025, 09:23 AM UTC
Duration
2h 50m
Affected: Matlantis (US)
Timeline · 3 updates
  1. investigating Dec 12, 2025, 06:32 AM UTC

    We are currently investigating this issue.

  2. identified Dec 12, 2025, 08:50 AM UTC

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

  3. resolved Dec 12, 2025, 09:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025

System is temporarily unavailable

Detected by Pingoru
Oct 20, 2025, 07:04 AM UTC
Resolved
Oct 20, 2025, 11:05 PM UTC
Duration
16h
Affected: Matlantis (Japan)Matlantis (US)Matlantis (EU)
Timeline · 8 updates
  1. investigating Oct 20, 2025, 07:04 AM UTC

    We are currently investigating this issue.

  2. investigating Oct 20, 2025, 07:37 AM UTC

    AWS is investigating increased error rates and latencies in the region. We are continuing to investigate the impact to Matlantis.

  3. investigating Oct 20, 2025, 07:57 AM UTC

    We are continuing to investigate this issue.

  4. monitoring Oct 20, 2025, 09:53 AM UTC

    The AWS team is seeing significant signs of recovery. We are monitoring the recovery of our systems.

  5. monitoring Oct 20, 2025, 10:04 AM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Oct 20, 2025, 10:25 AM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Oct 20, 2025, 10:26 AM UTC

    PFP Load Status remains unavailable. We continue to monitor the situation.

  8. resolved Oct 20, 2025, 11:05 PM UTC

    This incident has been resolved. There were minimal impacts in Japan and the EU region. For further details, please refer to the incident report.

Read the full incident report →

Major September 18, 2025

[Incident] LightPFP Notebook startup failure

Detected by Pingoru
Sep 18, 2025, 12:33 AM UTC
Resolved
Sep 18, 2025, 01:14 AM UTC
Duration
40m
Affected: Matlantis (Japan)Matlantis (US)Matlantis (EU)
Timeline · 6 updates
  1. investigating Sep 18, 2025, 12:33 AM UTC

    We are currently investigating this issue.

  2. identified Sep 18, 2025, 12:41 AM UTC

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

  3. identified Sep 18, 2025, 12:55 AM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Sep 18, 2025, 01:05 AM UTC

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

  5. monitoring Sep 18, 2025, 01:06 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Sep 18, 2025, 01:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 15, 2025

[Incident] System is temporarily unavailable

Detected by Pingoru
Apr 15, 2025, 08:03 AM UTC
Resolved
Apr 15, 2025, 09:10 AM UTC
Duration
1h 7m
Affected: Matlantis (Japan)
Timeline · 4 updates
  1. investigating Apr 15, 2025, 08:03 AM UTC

    We are currently investigating this issue.

  2. identified Apr 15, 2025, 08:33 AM UTC

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

  3. monitoring Apr 15, 2025, 08:50 AM UTC

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

  4. resolved Apr 15, 2025, 09:10 AM UTC

    This incident has been resolved.

Read the full incident report →