Incident: February 2nd - routing problem
- Michael Sahl
- Ilias Sersar
A routing problem at our service provider caused an outage of Microbizz. Even though the problem was fairly quickly resolved, the Microbizz internal network configuration failed to come up and had to be restarted the next morning.
| System availability | All web systems was unavailable |
|---|---|
| Data loss | No data is lost. |
| GDPR breach | No GDPR breach. |
Timeline
| February 2nd 21:26 GMT | A routing problem at our hosting provider caused all Microbizz servers to stop responding. Our provider reports: Our team is investigating a connectivity issue in our EU-Central (Frankfurt) data center. During this time, users may experience connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information. |
|---|---|
| February 2nd 22:06 GMT | The routing problem was resolved. Our provider reports: At this time we have been able to correct the issues affecting connectivity in our EU-Central (Frankfurt) data center. We will be monitoring this to ensure that it remains stable. Unfortunately the internal Microbizz network structure couldn't recover from this error, so Microbizz servers still didn't respond. |
| February 3rd 04:35 GMT | A Microbizz technician managed to restart the Microbizz network services and all systems are now operating normally. |