pingoru pingoru MB connect line had 9 outages in the last 2 years totaling 53h 41m of downtime, averaging 0.4 incidents per month.
There were 9 MB connect line outages since October 30, 2024 totaling 53h 41m of downtime. Each is summarised below. Incident details, duration, and resolution information.
This message was automatically generated by our monitoring system. The technical staff is now looking into the issue and will update this incident ASAP.
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.
Connecting is possible again without problems at the moment. We will continue monitoring the situation.
This incident has been resolved.
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
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
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.
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
This incident has been resolved
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.
This message was automatically generated by our monitoring system. The technical staff is now looking into the issue and will update this incident ASAP.
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.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.
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
The issue has been identified and a fix is being implemented.
This incident has been resolved.
This message was automatically generated by our monitoring system. The technical staff is now looking into the issue and will update this incident ASAP.
This message was automatically generated by our monitoring system. The technical staff is now looking into the issue and will update this incident ASAP.
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.