pingoru pingoru Fiftytwo had 9 outages in the last 2 years totaling 24h 55m of downtime, averaging 0.4 incidents per month.
There were 9 Fiftytwo outages since October 15, 2025 totaling 24h 55m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We're seeing disruptions on a few POS Services. If you are affected please be sure we're working on a solution ASAP
We identified the issue and resolved it for the few outliers. All systems operational once again. Thank you for your patience.
We are currently experiencing a heavy delay on POS and Store service activation and update requests. We are working hard on finding a solution.
The issue has been identified and we are working on deploying a fix as soon as possible. Expect and update within an hour
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We currently have an issue with POS activation and delivering transaction POS log events to customer topics Next update at 11.00
Transaction POS log events are being delivered again. We are still investigating the POS activating issue. Next update at 12.00
The issue with POS Activation have been found and we are currently working on a fix for this.
We are still working on a fix for the POS Activation issue. Next update at 13:00
We are currently validating our fix to the POS Activation issue. Next update at 14:00
A fix will be deployed to Production within the hour. The deployment will not affect current POS's. An update after the deployment will be posted.
A fix for the POS Activation has been deployed to production and has alleviated the issue.
We are currently investigating an ongoing issue with the POS service that is affecting some customers
We are continuing to investigate this issue.
The issue has been identified and we are working on a permanent issue. Current issue has been resolved
We're currently experiencing issues with the SMS provider to our Receipt text API service which is causing SMS messages to be delayed or to not be received entirely. We're in dialog with the provider to resume operations as soon as possible. We apologize for any inconvenience.
The issues at the provider seems to have been resolved and we are monitoring the results.
The incident is resolved, we observe no more issues from the SMS provider
An issue with sending receipt by SMS has been identified. The issue has been identify and a fix is being verified
Issue has been resolved and API is operational again
We are currently investigating an issue where requests to the API is responding with Http Status 502
We have identified the cause and are looking into fixing it.
We are verifying the fix and deploying it soon. All ordinary usages should not be affected - only a corner case.
We are working on a fix that will be hotfixed to the currently deployed application. A note of this will happen when it is done. For now the application is in a better state, but is being actively monitored.
We have pushed a fix to the Receipt API, resulting in a max allowed Limit on Get requests at 100.
Podhandler infrastructure update: Internal changes for preparation for upcoming store features
This incident has been resolved.
When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.
As you continue to work through the incident, update your customers frequently.
Let your users know once a fix is in place, and keep communication clear and precise.
Empathize with those affected and let them know everything is operating as normal.