pingoru pingoru Microbizz had 8 outages in the last 2 years totaling 98h 37m of downtime, averaging 0.3 incidents per month.
There were 8 Microbizz outages since December 3, 2024 totaling 98h 37m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We have identified the issues affecting these instances: Alert - System36 is experiencing issues Don't worry, our team of engineers are investigating.
All systems affected are operational again. Monitoring - System36 is operational Our engineers have applied a solution, we are now monitoring this instance.
One of our SMS gateways with the number +46769436112 is currently unresponsive. Text messages sent to this number is currently not processed. We are working on fixing the situation.
The SMS gateway is operating again and all messages have been delivered.
We have identified an issue where the system haven't prepared the day properly for some of our customers, such as opening time sheets, stamping the workplan and opening tasks. We expect to run this for the affected customers within the next few hours.
We are continuing to work on a fix for this issue.
We have now started the day preparation process for all customers affected and it is currently completing. We are monitoring the situation, but this should bring status back to normal.
This incident has been resolved.
We have identified a problem in the latest version (11.4) of the Microbizz iOS app. This version doesn't show pending question forms under individual tasks, so if a question form have been requested from Microbizz, it won't be visible in the iOS app. This is only an error on iOS. Android app works as expected. For users depending of this functionality and haven't upgraded we suggest keeping the upgrade back. For users who have upgraded, we have the following workarounds: 1) The user can fill in the form manually, but needs to be informed what forms to fill. 2) From the websystem a user can start the form and save it for later. Then it will become visible on iOS, but please note that this can trigger form actions. We expect a new version to be available withing 20-40 hours from this point.
We have submitted a new build for the app store with version 11.4.1 and it's pending review at Apple.
The new release is now released in the app store and is named 11.4.1 on iOS. On Android the newest version number is still 11.4 and works as expected.
We are aware that our users currently cannot configure new apps and for customers using the https://system.microbizz.dk/ endpoint, the API is not responding. The latter issue can be circumvented by using the endpoint attached to your customer server, such as https://system15.microbizz.dk/ or similar. We expect to have resolved this issue by 09:10 CET
We are continuing to investigate this issue.
We have now resolved the issue of configuring new apps and accessing the system-endpoint.
Most of our customers are currently experiencing an error message when trying to connect to Microbizz. We are on the case and expect to resolve the issue before 07:00 CET
We have solved the problem where our customers encountered an error message while logging onto their systems, and are monitoring the situation.
Vi er blevet opmærksomme på, at den netop udgivne Android-app med versionsnummer 10.1 indeholder et problem, som kan få den til at crashe på brugerens telefon. Vi arbejder på at udgive en ny version og opfordrer vores Androidbrugere til ikke at opgradere app'en på nuværende tidspunkt.
Der er nu en ny version af app'en tilgængelig på Google Play, hvor problemet er løst. Den nye app har versionsnummer 10.2, så hvis du ser dette versionsnummer på opdateringssiden, så er den sikker at opdatere til.
We are currently experiencing an issue with our service provider, resulting in downtime for certain servers. This may affect access to our systems and services. Our provider is actively working to resolve the issue, and we will provide updates as soon as more information becomes available. We apologize for the inconvenience and appreciate your patience while we work to restore normal operations.
We are continuing to monitor for any further issues.
This incident has been resolved.