Tilroy Outage History
Tilroy is up right nowPingoru has recorded 50 incidents for Tilroy: 19 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 1 of 720 (0%) |
| May 2026 | 3 | 2 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 556 (0%) |
Incidents, newest first
Minor September 22, 2026 Tilroy is not available. 5m Point Of Sale, E-commerce, Data management and reporting
Started Sep 22, 2026, 07:56 AM UTC· resolved Sep 22, 2026, 08:01 AM UTC
- investigating Sep 22, 2026, 07:56 AM UTC
At the moment Tilroy is not available. Use offline mode to continue. We are investigating and will send updates when more information is available.
- monitoring Sep 22, 2026, 07:59 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 22, 2026, 08:01 AM UTC
This incident has been resolved.
Notice May 18, 2026 Money counts - post incident info –
Started May 18, 2026, 01:53 PM UTC· resolved May 18, 2026, 01:53 PM UTC
- resolved May 18, 2026, 01:56 PM UTC
All offline sales are not yet processed , this will take until closing hours of the stores. The could result in wrong moneycounts this evening when closing the till. If you skip the moneycount today, tomorrow these will be fine. If you execute money count today, this will also be wrong tomorrow. Contact support for more information.
Major May 18, 2026 Reports of very slow Tilroy performance 1h 4m Point Of Sale, Data management and reporting
Started May 18, 2026, 11:16 AM UTC· resolved May 18, 2026, 12:21 PM UTC
- investigating May 18, 2026, 11:16 AM UTC
We are notified for slower Tilroy performance. This is under investigation.
- investigating May 18, 2026, 11:18 AM UTC
Tilroy not available at the moment.
- investigating May 18, 2026, 11:44 AM UTC
A problem was identified with one of the databases. The system is online again.
- monitoring May 18, 2026, 11:44 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 18, 2026, 12:06 PM UTC
We are continuing to monitor for any further issues.
- resolved May 18, 2026, 12:21 PM UTC
This incident has been resolved.
- postmortem May 19, 2026, 05:42 AM UTC
**Summary** On Monday 18 May 2026 around 13:00 \(local time\), our production database became unavailable for 26 minutes. The cluster recovered automatically and was fully back in service by 13:43. No data was lost. **Background** Our database runs as a three-node cluster: three identical copies of our data, kept in sync across three separate servers. One node is the primary - it accepts new data. The other two are secondaries - they continuously copy the primary. At least two of the three nodes must be online for the cluster to keep accepting data. If only one remains, the cluster intentionally stops, to prevent the servers from disagreeing on what the latest data is. What happened at around 13:05, the primary node started to slow down and stopped responding to the other two. Within seconds, the cluster automatically promoted one of the secondaries to be the new primary,a routine failover that should have been invisible to users. This time the failover did not complete cleanly. The new primary inherited a large backlog of unfinished work from the old primary and became overloaded while trying to clear it. At 13:14, the new primary hit a built-in safety mechanism : when a node is stuck and cannot complete its role change within 30 seconds, it shuts itself down so the rest of the cluster can move on. About 30 seconds later, at 13:15, the original primary, still trying to step down, hit the exact same safety mechanism and also shut itself down. With two of the three nodes down at the same time, the cluster fell below the two-node minimum and stopped accepting reads and writes. Recovery automatically restarted both failed nodes. They came back online around 13:40, a new primary was elected, and full service was restored at 13:43, with no manual intervention required. **Next steps** We are working together with our database supplier to identify the underlying root cause, it could be hardware related. A follow-up will be shared once those findings are confirmed
Notice May 11, 2026 Slow Tilroy performance related to customers 1h 18m Point Of Sale, E-commerce, Data management and reporting
Started May 11, 2026, 11:17 AM UTC· resolved May 11, 2026, 12:35 PM UTC
- investigating May 11, 2026, 11:17 AM UTC
We noticed slower Tilroy performance related to customers. This is under investigation.
- monitoring May 11, 2026, 11:45 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 11, 2026, 12:35 PM UTC
This incident has been resolved.
Minor April 9, 2026 We are again receiving messages of slow performance or broken images. this is under investigation 34m Point Of Sale
Started Apr 09, 2026, 10:27 AM UTC· resolved Apr 09, 2026, 11:01 AM UTC
- investigating Apr 09, 2026, 10:27 AM UTC
We are currently investigating this issue.
- resolved Apr 09, 2026, 11:01 AM UTC
This incident has been resolved.
Minor April 9, 2026 Reports of slow performance 23m Point Of Sale, Data management and reporting
Started Apr 09, 2026, 09:27 AM UTC· resolved Apr 09, 2026, 09:51 AM UTC
- investigating Apr 09, 2026, 09:27 AM UTC
We are receiving messages of slow performance or broken images. this is under investigation
- identified Apr 09, 2026, 09:39 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 09, 2026, 09:42 AM UTC
This should be ok now
- resolved Apr 09, 2026, 09:51 AM UTC
This incident has been resolved.
Minor March 25, 2026 Selecting products via search in Tilroy is not working 23m Point Of Sale
Started Mar 25, 2026, 08:22 AM UTC· resolved Mar 25, 2026, 08:46 AM UTC
- identified Mar 25, 2026, 08:22 AM UTC
We receive messages about problems with selecting searched products. We have identified the issue and implementing a fix.
- monitoring Mar 25, 2026, 08:35 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 25, 2026, 08:46 AM UTC
This incident has been resolved.
Notice March 23, 2026 reports of parked sales instead of processed 53m Point Of Sale
Started Mar 23, 2026, 11:15 AM UTC· resolved Mar 23, 2026, 12:09 PM UTC
- investigating Mar 23, 2026, 11:15 AM UTC
we get reports of sales being parked instead of finalised.
- investigating Mar 23, 2026, 11:22 AM UTC
We are continuing to investigate this issue.
- monitoring Mar 23, 2026, 11:22 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Mar 23, 2026, 11:25 AM UTC
Parked sales are being porcessed.
- resolved Mar 23, 2026, 12:09 PM UTC
This incident has been resolved.
Notice March 19, 2026 Errors when creating pdf documents 5h Point Of Sale, Data management and reporting
Started Mar 19, 2026, 07:49 AM UTC· resolved Mar 19, 2026, 12:49 PM UTC
- investigating Mar 19, 2026, 07:49 AM UTC
We noticed that there are errors when creating pdf documents like invoices and quotations, we are investigating the issue.
- identified Mar 19, 2026, 08:12 AM UTC
The issue has been identified and a fix is being implemented.
- identified Mar 19, 2026, 09:28 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Mar 19, 2026, 10:48 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 19, 2026, 12:49 PM UTC
This incident has been resolved.
- postmortem Mar 20, 2026, 03:05 PM UTC
## Incident Report: PDF generating Issues On 19/03/2026 , our platform experienced a service interruption , which prevented the creation of PDF invoices. We understand the significant impact this has on your daily operations, and we sincerely apologize for the inconvenience this caused. ## What happened? To generate invoices within our software, we use a background service that controls a digital browser \(similar to Chrome\) to format and prepare your documents as PDFs. In the past, we had to manually configure and update this browser to ensure it stayed compatible with our specific systems. ## What went wrong? Yesterday, an automatic update occurred within the browser software’s external environment. This new version unexpectedly became incompatible with our PDF module. The issue was particularly persistent because our systems are designed to automatically fetch the latest browser version upon startup. As a result, even rolling back to a previous version of our PDF software did not resolve the issue, as the system continued to install the new, incompatible browser version. This explains why it took longer than usual to fully restore the service. ## How was this resolved? Our engineering team has changed how the PDF module is structured to ensure long-term stability: * **Integrated Linking:** We have rebuilt the system so that the PDF module now directly manages its own specific browser version. They are now treated as a single, unified package. * **Guaranteed Compatibility:** This change ensures that the module and the browser can never "fall out of sync." If one is updated, the other is automatically and safely updated alongside it. * **Stabler Infrastructure:** We have migrated to a new technical foundation specifically optimized for these tasks, increasing the overall reliability of our document generation. ## Conclusion The outage was caused by an external update that no longer aligned with our manual configuration. By changing the underlying technology and giving the system full control over its own dependencies, we have eliminated this risk. This ensures that a similar compatibility issue cannot occur in the future. Thank you for your patience and for your continued trust in our platform.
Notice January 2, 2026 Automatische activatie van Peppol-facturatie vanaf 5 januari - Activation automatique de la facturation Peppol dès le 5 janvier – Point Of Sale
Started Jan 02, 2026, 10:14 AM UTC· resolved Jan 02, 2026, 10:14 AM UTC
- resolved Jan 02, 2026, 10:14 AM UTC
Beste klant, Vanaf 1 januari 2026 is het in België wettelijk verplicht om facturen tussen bedrijven (B2B) digitaal te versturen via het Peppol-netwerk. Tilroy is hier volledig op voorbereid en veel van onze klanten maken hier inmiddels al gebruik van. Om u te ondersteunen, zullen wij vanaf maandag 5 januari 2026 de Peppol-activatie inschakelen voor alle Belgische B2B-klanten die geregistreerd zijn om het PEPPOL netwerk (indien u deze optie geactiveerd heeft). Wat betekent dit concreet voor u? Automatische herkenning: Wanneer u een factuur opmaakt voor een klant met een geregistreerd Peppol-adres, zal Tilroy deze automatisch selecteren. Geen Peppol-adres gevonden? Indien uw klant niet geregistreerd is op het netwerk, ontvangt u een melding op uw scherm. U kunt de facturatie dan voortzetten op de klassieke wijze (bijvoorbeeld via e-mail of print). Heeft u vragen over de activatie of de werking van Peppol binnen Tilroy of wenst u Peppol te activeren in uw account ? Neem dan gerust contact op met onze supportafdeling. Cher client, Depuis le 1er janvier 2026, l’envoi de factures électroniques entre entreprises (B2B) via le réseau Peppol est devenu une obligation légale en Belgique. Tilroy est entièrement préparé à ce changement et bon nombre de nos clients utilisent déjà cette fonctionnalité. Pour vous accompagner, nous activerons l’envoi via Peppol, à partir du lundi 5 janvier 2026, pour tous les clients B2B belges enregistrés sur le réseau Peppol (à condition que vous ayez activé cette option). Qu’est-ce que cela signifie concrètement pour vous ? Reconnaissance automatique : Lorsque vous établissez une facture pour un client disposant d'une adresse Peppol enregistrée, Tilroy la sélectionnera automatiquement. Pas d’adresse Peppol trouvée ? Si votre client n'est pas enregistré sur le réseau, un message s'affichera sur votre écran. Vous pourrez alors choisir de poursuivre la facturation de manière classique (par exemple via e-mail ou impression). Avez-vous des questions sur l'activation ou le fonctionnement de Peppol au sein de Tilroy ? N'hésitez pas à contacter notre service support.
Minor January 2, 2026 Selecting Customers interupted –
Started Jan 02, 2026, 08:00 AM UTC· resolved Jan 02, 2026, 08:00 AM UTC
- resolved Jan 16, 2026, 09:51 AM UTC
At the moment (2/1) it's not possible to select a customer in Tilroy. We implemented a fix to solve this issue.
Notice December 12, 2025 Reports of delay in processing of stock and etickets 18h 47m Point Of Sale, E-commerce, Data management and reporting
Started Dec 12, 2025, 01:43 PM UTC· resolved Dec 13, 2025, 08:31 AM UTC
- investigating Dec 12, 2025, 01:43 PM UTC
We are aware that the processing of stock and etickets has a delay. This is under investigation.
- investigating Dec 12, 2025, 02:29 PM UTC
We are continuing to investigate this issue.
- investigating Dec 12, 2025, 04:15 PM UTC
We would like to inform you that the stock and e-tickets will be processed, it's is only a delay. We continue to investigate
- resolved Dec 13, 2025, 08:31 AM UTC
This incident has been resolved.
Notice December 4, 2025 Payment errors when using Mollie or PayNL 7m Point Of Sale
Started Dec 04, 2025, 03:15 PM UTC· resolved Dec 04, 2025, 03:23 PM UTC
- identified Dec 04, 2025, 03:15 PM UTC
when using Mollie or PayNL as payment provider we experiencing errors while paying. Estimated solution in 10 minutes.
- resolved Dec 04, 2025, 03:23 PM UTC
This incident has been resolved.
Notice December 3, 2025 Reports of searches not showing up recent data 1h 44m Point Of Sale, Data management and reporting
Started Dec 03, 2025, 01:37 PM UTC· resolved Dec 03, 2025, 03:22 PM UTC
- investigating Dec 03, 2025, 01:37 PM UTC
We are notified that searching for recent data does not always return the expected results. We are investigating the issue.
- identified Dec 03, 2025, 02:34 PM UTC
The issue has been identified
- monitoring Dec 03, 2025, 02:34 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 03, 2025, 03:22 PM UTC
This incident has been resolved.
Minor December 1, 2025 Reports of broken webshops 7m E-commerce
Started Dec 01, 2025, 02:37 PM UTC· resolved Dec 01, 2025, 02:44 PM UTC
- investigating Dec 01, 2025, 02:37 PM UTC
We are notified of slow webshop performance on some sites. This is being investigated.
- monitoring Dec 01, 2025, 02:38 PM UTC
This is solved, we are monitorring BOT traffic.
- resolved Dec 01, 2025, 02:44 PM UTC
The bot is blocked
Minor November 24, 2025 We register a higher number of errors about prices. 1h 42m Point Of Sale, E-commerce, Data management and reporting
Started Nov 24, 2025, 08:53 AM UTC· resolved Nov 24, 2025, 10:35 AM UTC
- investigating Nov 24, 2025, 08:53 AM UTC
We receive more calls as usual about errors on prices. This is under investigation.
- investigating Nov 24, 2025, 08:53 AM UTC
We are continuing to investigate this issue.
- identified Nov 24, 2025, 09:00 AM UTC
The issue has been identified and a fix is being implemented. We recommend to use the offline client.
- monitoring Nov 24, 2025, 09:26 AM UTC
A fix has been implemented and we are monitoring the results.
- identified Nov 24, 2025, 09:38 AM UTC
The issue has not been solved, we have identified the issue and are implementing a fix. It is recommended to use the offline client.
- monitoring Nov 24, 2025, 09:51 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Nov 24, 2025, 10:35 AM UTC
This incident has been resolved.
- postmortem Nov 24, 2025, 11:00 PM UTC
On 25/11 at 09:50, the core Point-of-Sale \(POS\) and backend API services experienced a severe performance degradation, leading to transactional timeouts and a critical slowdown across retail operations. The incident was triggered by a corruption of a primary index on the MongoDB collection. This caused queries to bypass the fast index and perform costly full collection scans, which rapidly consumed all available CPU and I/O resources. The resulting database congestion caused the application to have timeouts. The issue was resolved by rebuilding the index, restoring full service. Because of the size and load this took more than half an hour. We sincerely apologize for the disruption and the resulting inability to process transactions efficiently for the duration of the incident. We understand that peak performance is critical to your daily retail operations, and this incident fell short of the reliability standard you expect from our product. We confirm that customers utilizing the offline functionality were able to continue processing sales locally. All transactions recorded offline during the database degradation period were successfully synced to the central database immediately after the service was restored, ensuring no loss of sales data. Thank you for your patience during this incident.
Notice October 31, 2025 !! New Google Chrome Update Blocking Local client !! – Point Of Sale
Started Oct 31, 2025, 10:13 AM UTC· resolved Oct 31, 2025, 10:13 AM UTC
- resolved Oct 31, 2025, 10:13 AM UTC
Google Chrome is pushing an upgrade. After the update you will see a popup to block or allow access to LOCAL NETWERK. It's important to allow this to continue working with your local client. Select ALLOW if you get this popup. If you selected "BLOCK", you need to change this to "ALLOW" using the site settings in Chrome. We will mail detailed information to all customers. If you experience the problem and need help mailt to [email protected]
Notice October 20, 2025 An error message is displayed when processing goods receipts in store. 1h 44m Point Of Sale, Data management and reporting
Started Oct 20, 2025, 12:59 PM UTC· resolved Oct 20, 2025, 02:44 PM UTC
- identified Oct 20, 2025, 12:59 PM UTC
Customers are encountering an error message when processing goods receipts in store. However the transfer completes successfully, and the goods receipt is finalized without any problem. Our team is actively investigating and expects to deploy a fix later today. We apologize for any inconvenience and appreciate your patience.
- resolved Oct 20, 2025, 02:44 PM UTC
This incident has been resolved.
Minor September 6, 2025 Reports of failing payments 6h 12m Point Of Sale
Started Sep 06, 2025, 03:26 PM UTC· resolved Sep 06, 2025, 09:39 PM UTC
- investigating Sep 06, 2025, 03:26 PM UTC
We receive a higher number of error reports in finalizing a sale. This is under investigation.
- monitoring Sep 06, 2025, 03:28 PM UTC
The situation normalized.
- resolved Sep 06, 2025, 09:39 PM UTC
This incident has been resolved.
Notice July 24, 2025 Zoined Integration delay 1d Data management and reporting
Started Jul 24, 2025, 05:52 AM UTC· resolved Jul 25, 2025, 06:09 AM UTC
- identified Jul 24, 2025, 05:52 AM UTC
Since yesterday we noticed delays in processing data to the reporting platform zoined. You could see incomplete sales data from yesterday. This is under investigation and we expect this will be solved today.
- identified Jul 24, 2025, 05:15 PM UTC
We expect all data will be processed by tomorrow (25/07) early morning.
- resolved Jul 25, 2025, 06:09 AM UTC
All data is processed.
Notice July 3, 2025 Product upload is not working 1h 45m Point Of Sale, E-commerce, Data management and reporting
Started Jul 03, 2025, 12:52 PM UTC· resolved Jul 03, 2025, 02:38 PM UTC
- investigating Jul 03, 2025, 12:52 PM UTC
We receive messages about problems with product uploads. This is under investigation.
- monitoring Jul 03, 2025, 12:58 PM UTC
A fix has been implemented, we are processing the backlog.
- resolved Jul 03, 2025, 02:38 PM UTC
This incident has been resolved.
Major June 19, 2025 Postmortem info added - Tilroy is not available. 8m Point Of Sale, Data management and reporting
Started Jun 19, 2025, 06:17 AM UTC· resolved Jun 19, 2025, 06:26 AM UTC
- identified Jun 19, 2025, 06:17 AM UTC
At the moment Tilroy is not available. Use offline mode to continue. We are investigating and will send updates when more information is available.
- identified Jun 19, 2025, 06:20 AM UTC
We have identified the problem, it should be solved in 15 minutes.
- resolved Jun 19, 2025, 06:26 AM UTC
This incident has been resolved.
- postmortem Jun 19, 2025, 09:23 AM UTC
Between **08:15 and 08:21** on 19/06/2025, the Tilroy platform experienced a short disruption that temporarily blocked many sales transactions. Although the rest of the system remained available stores and webshops were unable to complete sales during this window. This interruption was caused by a backend issue in our messaging infrastructure. In that five-minute period, a significant number of the components responsible for this messaging process \(called "nodes"\) began to fail simultaneously. Our automated infrastructure immediately started replacing the failed nodes, which restored the system within minutes. However, during the recovery process, sales operations were temporarily halted because the platform couldn’t complete the essential communication steps needed to start or finalize a sale. We know every minute matters in retail. Once our internal analysis is complete, we will share more details about the cause and the improvements being implemented in next releasenotes.
Major June 16, 2025 Webshops are not available. 1h 21m E-commerce
Started Jun 16, 2025, 09:40 AM UTC· resolved Jun 16, 2025, 11:01 AM UTC
- identified Jun 16, 2025, 09:40 AM UTC
At the moment some webshops are not available. We are investigating and will send updates when more information is available.
- monitoring Jun 16, 2025, 10:05 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 16, 2025, 11:01 AM UTC
This incident has been resolved.
- postmortem Jun 17, 2025, 05:18 AM UTC
On 16/06/2024, multiple webshops experienced issues loading certain product detail pages. A number of these pages returned errors, resulting in a broken user experience . The incident was traced back to a data anomaly in the product information, specifically a glitch that led to malformed product records. A glitch during product updates introduced invalid or incomplete fields in a small subset of products. These data inconsistencies were not previously accounted for in the logic of our frontend rendering layer. As a result, when such records were accessed, the PDPs failed to load properly. The immediate fix involved correcting the malformed product data. Once the affected entries were updated and revalidated in the system, the product pages began rendering normally again. We apologize for the inconvenience this incident may have caused to our customers and users. At Tilroy, we want to ensure a smooth and reliable shopping experience, and we understand that even brief interruptions can be frustrating. We appreciate your patience and trust as we work to improve our systems and prevent such issues from occurring again.
Minor May 28, 2025 We register a higher number of errors. 9m Point Of Sale, Data management and reporting
Started May 28, 2025, 09:57 AM UTC· resolved May 28, 2025, 10:07 AM UTC
- investigating May 28, 2025, 09:57 AM UTC
We receive more calls as usual about Tilroy not working or slow operation. This is under investigation.
- investigating May 28, 2025, 09:57 AM UTC
We are continuing to investigate this issue.
- resolved May 28, 2025, 10:07 AM UTC
This incident has been resolved.
- postmortem May 28, 2025, 11:29 AM UTC
This morning Tilroy experienced a short interuption. At 11:53 some customer received errors, this was solved at 11:56. This was caused by a database server problem. The system swicthed over to another server in the cluster causing a short interuption for some transactions. Kind regard
Notice May 5, 2025 We register a higher number of errors when logging in. 17m Point Of Sale, Data management and reporting
Started May 05, 2025, 12:20 PM UTC· resolved May 05, 2025, 12:38 PM UTC
- investigating May 05, 2025, 12:20 PM UTC
We receive more calls as usual about Tilroy not working or slow operation. This is under investigation.
- monitoring May 05, 2025, 12:33 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 05, 2025, 12:38 PM UTC
This incident has been resolved.