MB connect line Outage History

MB connect line is up right now

MB connect line had 9 outages in the last 2 years totaling 54h 5m of downtime — averaging 0.4 incidents per month.

There were 9 MB connect line outages since October 30, 2024 totaling 54h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.mbconnectline.com

Minor September 24, 2026

Temporary Service Disruption

Detected by Pingoru
Sep 24, 2026, 01:45 PM UTC
Resolved
Sep 24, 2026, 03:20 PM UTC
Duration
1h 35m
Affected: mbCONNECT24 Europe V2
Timeline · 3 updates
  1. identified Sep 24, 2026, 02:43 PM UTC

    Due to a temporary increase in server load on our rsp.mbCONNECT24 (EU) S1, the server was briefly unavailable. As a result, some connections were interrupted, but they have since been successfully restored. Our technical team will be investigating the incident and taking appropriate action to prevent further impact.

  2. monitoring Sep 24, 2026, 02:53 PM UTC

    Connecting is possible again without problems at the moment. We will continue monitoring the situation.

  3. resolved Sep 24, 2026, 03:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 14, 2026

Connectivity Issues

Detected by Pingoru
Sep 14, 2026, 06:30 AM UTC
Resolved
Sep 14, 2026, 09:36 AM UTC
Duration
3h 6m
Affected: mbCONNECT24 Europe V2mbCONNECT24 Europe S2
Timeline · 6 updates
  1. investigating Sep 14, 2026, 06:30 AM UTC

    We are experiencing connectivity issues with our system, we are in close contact with our hoster to locate the issue. The R&D team is informed and the situation is being investigated. Users of the system might have problems connecting to the system. We will keep you updated

  2. identified Sep 14, 2026, 06:57 AM UTC

    There has been an unplanned host migration at our hoster last night, which presumably led to the situation we are in now. We have already started the steps that are needed to restore the connectivity again and we will keep you updated

  3. monitoring Sep 14, 2026, 07:44 AM UTC

    A fix has been implemented. Routers that have lost their connections are reconnecting and your mbDIALUP connection should be possible again too shortly, due to the high load of incoming connections, the login process might still be a little delayed.

  4. monitoring Sep 14, 2026, 08:34 AM UTC

    We are continuing to monitor the server status. As of right now, the recovery process seems to continue as it should. Our team keeps monitoring the situation

  5. resolved Sep 14, 2026, 09:36 AM UTC

    This incident has been resolved

  6. postmortem Sep 14, 2026, 09:42 AM UTC

    Due to a hardware failure at our hoster, they needed to replace the host which hosted our rsp.mbCONNECT24 EU S1/S2/S3 server instances as well as our Gatekeeper. During the migration process to another host, the systems needed to be restarted simultaneously which led to some technical issues. We were able to resolve the situation again without the need of another full restart, at around 9am, the VPN connections to our S1 server were reconnecting and at around 10:30, most connections were back again. Due to the higher load, the login process was still impaired for a little while. We are in close contact with our hoster to make sure to prevent this for future situations.

Read the full incident report →

Minor August 18, 2026

Temporary connectivity issues

Detected by Pingoru
Aug 18, 2026, 07:43 AM UTC
Resolved
Aug 18, 2026, 12:21 PM UTC
Duration
4h 38m
Affected: mbCONNECT24 Europe V2mbCONNECT24 Europe S2mbCONNECT24 Europe V1
Timeline · 5 updates
  1. investigating Aug 18, 2026, 07:43 AM UTC

    We are currently experiencing temporary connectivity issues caused by planned maintenance on our hosting provider's side. As a result, some users may have trouble connecting to the system. For more details, please see: https://hosted-private-cloud.status-ovhcloud.com/ We will notify you as soon as the system is fully operational again. Thank you for your patience.

  2. monitoring Aug 18, 2026, 07:43 AM UTC

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

  3. monitoring Aug 18, 2026, 07:53 AM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Aug 18, 2026, 08:19 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Aug 18, 2026, 12:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 9, 2026

Login and Web2Go issues

Detected by Pingoru
Jul 09, 2026, 10:29 AM UTC
Resolved
Jul 09, 2026, 11:23 AM UTC
Duration
53m
Affected: mbCONNECT24 USA V2
Timeline · 3 updates
  1. investigating Jul 09, 2026, 10:29 AM UTC

    We are currently investigating reports of issues affecting login and Web2Go. Some users may experience errors or delays when trying to sign in or access Web2Go. We are actively working to identify the root cause and will provide an update as soon as more information is available. Affected services: Login, Web2Go

  2. identified Jul 09, 2026, 11:03 AM UTC

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

  3. resolved Jul 09, 2026, 11:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 30, 2025

Connectivity issue

Detected by Pingoru
May 30, 2025, 03:30 PM UTC
Resolved
May 30, 2025, 03:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 30, 2025, 04:27 PM UTC

    We were experiencing a connectivity issue with our mbCONNECT24 EU V1 system, due to a host failure at our hosters data center. Our automatic failover stepped in and kept the downtime to a minimum, however, some connections were lost and had to re-connect again. The system is up and running again as usual.

Read the full incident report →

Critical October 30, 2024

Abnormal situtation automatically detected on: mbCONNECT24 Europe V1

Detected by Pingoru
Oct 30, 2024, 01:25 PM UTC
Resolved
Oct 30, 2024, 02:05 PM UTC
Duration
40m
Affected: mbCONNECT24 Europe V1
Timeline · 2 updates
  1. investigating Oct 30, 2024, 01:25 PM UTC

    This message was automatically generated by our monitoring system. The technical staff is now looking into the issue and will update this incident ASAP.

  2. resolved Oct 30, 2024, 02:05 PM UTC

    This incident has been resolved.

Read the full incident report →