Pagero Outage History

Started Oct 09, 2026, 11:20 AM UTC· resolved Oct 09, 2026, 09:26 PM UTC

1. investigating Oct 09, 2026, 11:20 AM UTC

   We are currently experiencing intermittent issues that may impact various services in Pagero Online. Our teams are actively investigating and working to restore full stability as quickly as possible. Customers may experience occasional disruptions or degraded performance during this time. We apologize for any inconvenience and will post new updates as soon as we learn anything more.

2. investigating Oct 09, 2026, 01:21 PM UTC

   We are still experiencing intermittent issues that may impact various services in Pagero Online. Our teams continue to investigate the root cause and are working to restore full stability as quickly as possible. Customers may continue to experience occasional disruptions or degraded performance during this time. We apologize for the inconvenience and will provide further updates as soon as more information becomes available.

3. monitoring Oct 09, 2026, 02:14 PM UTC

   Our technical team has implemented corrective measures, and services are currently operating normally. We will continue to monitor the situation closely to ensure continued stability and will provide a further update once the incident is fully resolved. Thank you for your patience and understanding.

4. resolved Oct 09, 2026, 09:26 PM UTC

   We have continued to monitor the situation, and all services are operating normally. As stability has been confirmed, this incident is now considered resolved. Thank you for your patience and understanding.

Read the full incident report →

Started Oct 01, 2026, 07:46 AM UTC· resolved Oct 01, 2026, 09:14 AM UTC

1. investigating Oct 01, 2026, 07:46 AM UTC

   We are currently experiencing downtime with our integration platform, affecting nearly all incoming and outgoing files to and from TMS.

2. monitoring Oct 01, 2026, 08:46 AM UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring Oct 01, 2026, 08:56 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Oct 01, 2026, 09:14 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 25, 2026, 12:35 PM UTC· resolved Sep 25, 2026, 06:53 PM UTC

1. investigating Sep 25, 2026, 12:35 PM UTC

   We are currently investigating intermittent service disruptions affecting Pagero Online France. Customers may experience slow response times, timeout errors, or intermittent failures when accessing administrative functions. Our technical teams are actively investigating the issue. We apologize for the inconvenience and will share additional updates as soon as we have more information. If you have any questions, please contact our Support team

2. monitoring Sep 25, 2026, 02:34 PM UTC

   The affected services have recovered and are operating normally. We identified and mitigated an issue impacting internal service communications, which caused intermittent errors and slow response times for some users. We are continuing to monitor the environment to ensure stability. If you have any questions, please contact our Support team

3. resolved Sep 25, 2026, 06:53 PM UTC

   The issue has now been resolved and services are available and working as normal. We apologize for any inconvenience this might have caused. If you have any questions, please contact our Support team

Read the full incident report →

Started Sep 24, 2026, 01:00 PM UTC· resolved Sep 24, 2026, 07:55 PM UTC

1. investigating Sep 24, 2026, 01:00 PM UTC

   Due to a system update, some attachments that are not normally included may have been sent between 10:10 and 12:30. These attachments may appear as though they are regular documents in an incorrect format, or they may show as attachments with incorrect file naming conventions according to your setup. Please disregard any files that you were not expecting to receive. If you would like us to resend the files so that only the relevant documents are delivered, please feel free to contact us and we will be happy to assist.

2. resolved Sep 24, 2026, 07:55 PM UTC

   Our advanced technical team has investigated the issue and successfully reprocessed all affected documents. The relevant files have now been processed correctly in accordance with your configured format and file-naming conventions. Please disregard any unexpected or incorrectly formatted files received during the affected period. If you have any questions or would like us to resend specific documents, please contact us at Support.

Read the full incident report →

Started Sep 16, 2026, 09:49 AM UTC· resolved Sep 16, 2026, 08:24 PM UTC

1. investigating Sep 16, 2026, 09:49 AM UTC

   Dear Customers We are suffering some interruptions in the system that allows you to communicate with us via Chat and Email. While the issue does not prevent the communication, it can make it longer for us to respond. We apologize for any inconvenience this may cause and appreciate your patience. We will update this notice once the issue has been resolved.

2. identified Sep 16, 2026, 01:29 PM UTC

   We have identified the cause of the current slowness in our Support case handling as a global disruption at our external service provider, Salesforce, confirmed on their own status page. Chat and phone support remain available, and cases submitted are being received as normal. However, processing of cases is currently slower than usual due to this disruption. We are monitoring the situation and will post an update as soon as Salesforce resolves the issue, or with further information. We apologize for any inconvenience.

3. identified Sep 16, 2026, 03:55 PM UTC

   The slowness as a global disruption in our Support case handling system at our external service provider still persists. Chat and phone support remain available, and cases submitted are being received as normal. However, processing of cases is currently slower than usual due to this disruption. We are still monitoring the situation and will post an update as soon as our vendor resolves the issue, or with further information.

4. investigating Sep 16, 2026, 08:23 PM UTC

   The issue has now been resolved, and services are available and working as normal. The external service provider has confirmed that instance stability and performance have returned to expected levels and the incident has been declared resolved. The external service provider is conducting a thorough investigation to identify the technical trigger and underlying cause, as well as preventive actions to help avoid a recurrence. We will share further information about the cause of the issue as it becomes available. We apologise for any inconvenience this might have caused.

5. resolved Sep 16, 2026, 08:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 15, 2026, 11:07 AM UTC· resolved Sep 15, 2026, 05:46 PM UTC

1. investigating Sep 15, 2026, 11:07 AM UTC

   We're currently investigating reports of a potential disruption to the connection with KSeF, which may be causing missing / delayed application responses. We are working to identify the cause and assess the impact on customers. We apologize for any inconvenience and will provide further updates as soon as we learn more. If you have any questions, please contact our Support team

2. identified Sep 15, 2026, 01:42 PM UTC

   We've identified the cause of the issue affecting KSeF document processing. Due to unusually high traffic, some documents may take longer than usual to process, and in some cases uploads may need to be retried. We're working on improvements to reduce delays and restore normal processing as quickly as possible. If you have any questions, please contact our Support team

3. resolved Sep 15, 2026, 05:46 PM UTC

   The issue has now been resolved and services are available and working as normal. We apologize for any inconvenience this might have caused. Our advanced technical team identified the root cause and resent all affected jobs. More information about the underlying cause will be shared when available. If you have any questions, please contact our Support team

Read the full incident report →

Started Sep 15, 2026, 08:23 AM UTC· resolved Sep 15, 2026, 01:50 PM UTC

1. investigating Sep 15, 2026, 08:23 AM UTC

   We have received information from our partner Masters India pointing to a disturbance since 10:00 am (CET) that could possibly affect the document flow towards the Indian Tax Authority (NIC). This may affect our customers who use the Indian Clearance service. For more information from Masters India, see below. We are currently experiencing a service disruption. Our team is actively working to resolve the issue, and we expect to restore service shortly.

2. identified Sep 15, 2026, 11:07 AM UTC

   We have been informed by our partner that the issue has been resolved. However, some documents may still remain in a pending status. We are working to process the remaining documents as soon as possible. If you have any questions, please contact our Support team

3. resolved Sep 15, 2026, 01:50 PM UTC

   The issue has now been resolved and services are available and working as normal. We apologize for any inconvenience this might have caused. If you have any questions, please contact our Support team

Read the full incident report →

Started Aug 31, 2026, 08:44 AM UTC· resolved Aug 31, 2026, 10:42 AM UTC

1. investigating Aug 31, 2026, 08:44 AM UTC

   Dear Customer, We are currently experiencing timeout issues affecting user logins to the Health Invoice service. Users may encounter delayed responses or login failures when attempting to access the application. Our technical team is actively investigating the issue and working to restore normal service as quickly as possible. We apologize for any inconvenience and will provide further updates as they become available. Kind regards Pagero Support *************************************************************************** Sehr geehrte Kunden, wir haben derzeit Timeout-Probleme bei der Anmeldung im Health Invoice. Benutzer können beim Zugriff auf die Anwendung verzögerte Reaktionen oder fehlgeschlagene Anmeldeversuche feststellen. Unser technisches Team untersucht die Ursache des Problems bereits und arbeitet daran, den regulären Betrieb schnellstmöglich wiederherzustellen. Wir entschuldigen uns für die entstandenen Unannehmlichkeiten und werden weitere Informationen bereitstellen, sobald diese verfügbar sind. Mit freundlichen Grüßen Pagero Support

2. resolved Aug 31, 2026, 10:42 AM UTC

   Dear Customer, The login issue in Health Invoice has been resolved. Users can login again as usual. We apologize for any inconvenience. Kind regards Pagero Support *************************************************************************** Sehr geehrte Kunden, das Login Problem in Health Invoice wurde behoben. Sie können sich wieder wie gewohnt anmelden. Wir entschuldigen uns für die entstandenen Unannehmlichkeiten. Mit freundlichen Grüßen Pagero Support

Read the full incident report →

Started Aug 20, 2026, 06:54 AM UTC· resolved Aug 20, 2026, 09:16 AM UTC

1. investigating Aug 20, 2026, 06:54 AM UTC

   We are currently investigating reports of a possible outage of Health Mobile. We are currently investigating the root cause . We apologize for any inconvenience and will post new updates as soon as we have more information. If you have any questions, please contact our Support team ************************* Wir untersuchen derzeit Berichte über einen möglichen Ausfall eines oder mehrerer Dienste in unserem Health Mobile. Wir arbeiten daran, die Ursache zu ermitteln. Wir entschuldigen uns für etwaige Unannehmlichkeiten und werden neue Updates veröffentlichen, sobald wir mehr erfahren. Wenn Sie Fragen haben, wenden Sie sich bitte an unser Support team

2. monitoring Aug 20, 2026, 07:59 AM UTC

   We believe to have fixed the issue and see successful Health Mobile transactions flowing now. We're monitoring to be sure everything's back to working. We apologize for any inconvenience and will post new updates as soon as we have more information. If you have any questions, please contact our Support team ************************* Wir gehen davon aus, dass wir das Problem behoben haben und sehen nun wieder erfolgreich durchlaufende Health Mobile-Transaktionen. Derzeit überwachen wir das System weiterhin, um sicherzustellen, dass alles wieder ordnungsgemäß funktioniert. Wir entschuldigen uns für etwaige Unannehmlichkeiten und werden neue Updates veröffentlichen, sobald wir mehr erfahren. Wenn Sie Fragen haben, wenden Sie sich bitte an unser Support team

3. resolved Aug 20, 2026, 09:16 AM UTC

   ONESOURCE Pagero Health Mobile has been running stably for over an hour. We thank you for your patience and apologize again for any inconvenience caused. ************************ ONESOURCE Pagero Health Mobile läuft seit über einer Stunde stabil. Wir danken Ihnen für Ihre Geduld und bitten für für die entstandenen Unannehmlichkeiten nochmals um Entschuldigung.

Read the full incident report →

Started Aug 12, 2026, 10:00 AM UTC· resolved Aug 12, 2026, 01:04 PM UTC

1. investigating Aug 12, 2026, 10:00 AM UTC

   We are currently investigating degraded performance affecting Pagero Online's AS2 inbound service. The service is experiencing elevated latency due to high resource usage. As a result, some external inbound traffic may experience timeouts or similar connectivity issues, although the service continues to process a portion of traffic. Our technical teams are actively working to reduce the load on affected service instances and restore normal performance. We will provide further updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.

2. resolved Aug 12, 2026, 01:04 PM UTC

   Pagero Online's AS2 inbound service has been restored to normal performance. The elevated latency and intermittent connectivity issues affecting some external inbound traffic have been resolved. Our technical teams reduced the resource usage on the affected service instances, and inbound processing is operating normally. We apologize for the inconvenience and thank you for your patience.

Read the full incident report →

Started Jul 03, 2026, 02:36 AM UTC· resolved Jul 03, 2026, 03:56 AM UTC

1. resolved Jul 03, 2026, 11:49 AM UTC

   Unfortunately we detected a malfunction in one of the Pagero Health Services AS2 services today, the 3rd of July 26. The outage was between 04:36 AM CEST and 05:56 AM CEST today. The service is completely available now. If you had trouble sending messages to our AS2 during that time frame please repeat the transmission! This only affected you when sending to the following URL: https://as2prod.pagerohealth.com:443/as2/HttpReceiver https://as2prod.pagerohealth.com:80/as2/HttpReceiver and following AS2IDs: PAGEROHEALTH24 PAGEROHEALTH24P If you have any questions, please contact our Support team We apologize for any inconvenience caused

Read the full incident report →

Started Jun 24, 2026, 03:34 PM UTC· resolved Jun 25, 2026, 06:01 AM UTC

1. identified Jun 24, 2026, 03:34 PM UTC

   We are currently investigating an issue affecting some payment files sent from Pagero Online, mainly towards SEB and Handelsbanken. The issue was identified at 15:30 CEST and may cause affected files to be rejected or not accepted due to missing required data. We are working on resolving the issue, and a fix is currently in progress. Once the fix has been deployed, we will reprocess the affected files. Unfortunately, affected files will need to be signed again in Pagero Online. We apologize for any inconvenience and will post new updates as soon as we learn anything more. If you have any questions, please contact our Support team

2. resolved Jun 25, 2026, 06:01 AM UTC

   The issue has now been resolved and services are available and working as normal. All affected files have been reprocessed. Please note that the affected files will need to be signed again in Pagero online. Make sure you are not reuploading duplicate files if you received an error notification. The issue was caused by an update that had the unintended consequence where the PAIN001 file that is created by Pagero and sent to the bank, not having all the mandatory data. We apologize for any inconvenience this might have caused. If you have any questions, please contact our Support team

Read the full incident report →

Started Jun 19, 2026, 10:20 AM UTC· resolved Jun 22, 2026, 05:17 PM UTC

1. investigating Jun 19, 2026, 10:20 AM UTC

   Our support email address, [email protected], is currently experiencing technical difficulties and is temporarily unavailable. Any emails sent to this address will not be received by our support team. While we work to resolve this issue, we kindly ask you to use one of the following alternative channels to submit a support case: -Support Site: https://www.thomsonreuters.com/en-us/help/pagero/online -Chat: Available through our support site -Phone: Please contact us directly via our support phone line We apologize for any inconvenience this may cause and appreciate your patience. We will update this notice once the issue has been resolved. If you have any questions, please contact our Support team

2. investigating Jun 19, 2026, 10:25 AM UTC

   We are continuing to investigate this issue.

3. investigating Jun 19, 2026, 03:56 PM UTC

   We are continuing to investigate this issue.

4. investigating Jun 19, 2026, 10:00 PM UTC

   We are continuing to investigate the technical issue. At this time, emails sent to [email protected] address may not be received by our support team. While we work to resolve the issue, please continue to submit support cases through one of the following alternative channels: Support Site: https://www.thomsonreuters.com/en-us/help/pagero/online Chat: Available through our support site Phone: Please contact us directly via our support phone line We apologize for the inconvenience and will provide an update again in 4 hours time, or once the issue has been resolved.

5. investigating Jun 20, 2026, 02:00 AM UTC

   We are continuing to investigate the technical issue. While we work to resolve it, please continue to submit support cases through one of the following alternative channels: Support Site: https://www.thomsonreuters.com/en-us/help/pagero/online Chat: Available through our support site Phone: Please contact us directly via our support phone line We apologize for the inconvenience and will provide an update again in 4 hours time, or once the issue has been resolved.

6. investigating Jun 20, 2026, 06:13 AM UTC

   This issue is still under investigation. We will update the information as soon as new findings are made. While we work to resolve the issue, please continue to submit support cases through one of the following alternative channels: Support Site: https://www.thomsonreuters.com/en-us/help/pagero/online Chat: Available through our support site Phone: Available on our contact information We apologize for the inconvenience and will provide an update again in 4 hours time, or once the issue has been resolved.

7. investigating Jun 20, 2026, 01:21 PM UTC

   This issue is still under investigation. Unfortunately, there is no new information that can be shared, but we will post updates accordingly once new information becomes available. While we work to resolve the issue, please continue to submit support cases through one of the following alternative channels: Support Site: https://www.thomsonreuters.com/en-us/help/pagero/online Chat: Available through our support site Phone: Available on our contact information We apologize for the inconvenience and will provide an update again in 4 hours time, or once the issue has been resolved.

8. investigating Jun 20, 2026, 09:25 PM UTC

   This issue is still under investigation. Unfortunately, there is no new information that can be shared, but we will post updates accordingly once new information becomes available. While we work to resolve the issue, please continue to submit support cases through one of the following alternative channels: Support Site: https://www.thomsonreuters.com/en-us/help/pagero/online Chat: Available through our support site Phone: Available on our contact information We apologize for the inconvenience and will provide an update again in 4 hours time, or once the issue has been resolved.

9. investigating Jun 21, 2026, 04:08 AM UTC

   This issue is still under investigation. Unfortunately, there is no new information that can be shared, but we will post updates accordingly once new information becomes available. While we work to resolve the issue, please continue to submit support cases through one of the following alternative channels: Support Site: https://www.thomsonreuters.com/en-us/help/pagero/online Chat: Available through our support site Phone: Available on our contact information We apologize for the inconvenience and will provide an update again in 4 hours time, or once the issue has been resolved.

10. investigating Jun 21, 2026, 01:23 PM UTC

    This issue is still under investigation. Unfortunately, there is no new information that can be shared, but we will post updates accordingly once new information becomes available. While we work to resolve the issue, please continue to submit support cases through one of the following alternative channels: Support Site: https://www.thomsonreuters.com/en-us/help/pagero/online Chat: Available through our support site Phone: Available on our contact information We apologize for the inconvenience and will provide an update again in 4 hours time, or once the issue has been resolved.

11. investigating Jun 21, 2026, 08:52 PM UTC

    This issue is still under investigation. Unfortunately, there is no new information that can be shared, but we will post updates accordingly once new information becomes available. While we work to resolve the issue, please continue to submit support cases through one of the following alternative channels: Support Site: https://www.thomsonreuters.com/en-us/help/pagero/online Chat: Available through our support site Phone: Available on our contact information We apologize for the inconvenience and will provide an update again in 4 hours time, or once the issue has been resolved.

12. investigating Jun 22, 2026, 04:01 AM UTC

    This issue is still under investigation. Unfortunately, there is no new information that can be shared, but we will post updates accordingly once new information becomes available. While we work to resolve the issue, please continue to submit support cases through one of the following alternative channels: Support Site: https://www.thomsonreuters.com/en-us/help/pagero/online Chat: Available through our support site Phone: Available on our contact information We apologize for the inconvenience and will provide an update again in 4 hours time, or once the issue has been resolved.

13. resolved Jun 22, 2026, 05:17 PM UTC

    This incident has now been resolved and the service is operating normally. We apologize for the disruption and any inconvenience caused. We've implemented improved processes and automation to help prevent this from happening again.

Read the full incident report →

Started Jun 15, 2026, 06:48 AM UTC· resolved Jun 15, 2026, 07:49 AM UTC

1. monitoring Jun 15, 2026, 06:48 AM UTC

   Unfortunately we detected a malfunction in one of the Pagero Health Services AS2 service today, the 15th of June. The outage was between 02:09 AM CEST and 08:13 AM CEST today. The service is completely available now. If you had trouble sending messages to our AS2 during that time frame please repeat the transmission! This only affected you when sending to the following URL: https://as2prod.pagerohealth.com:443/as2/HttpReceiver https://as2prod.pagerohealth.com:80/as2/HttpReceiver and following AS2IDs: PAGEROHEALTH24 PAGEROHEALTH24P If you have any questions, please contact our Support team We apologize for any inconvenience caused ************************** Leider haben wir heute, am 15, Juni eine Fehlfunktion in einem der Pagero Health Services AS2-Dienste festgestellt. Der Ausfall trat zwischen dem 02:09 Uhr MEZ und 08:13 Uhr MEZ auf. Der Dienst ist jetzt wieder komplett verfügbar. Wenn Sie während dieses Zeitraums Probleme beim Senden von Nachrichten an unseren AS2-Dienst hatten, wiederholen Sie bitte die Übertragung! Dies betraf Sie nur beim Senden an die folgenden URLs: https://as2prod.pagerohealth.com:443/as2/HttpReceiver https://as2prod.pagerohealth.com:80/as2/HttpReceiver und die folgenden AS2IDs: PAGEROHEALTH24 PAGEROHEALTH24P Wenn Sie Fragen haben, wenden Sie sich bitte an unser Support-Team. Wir entschuldigen uns für die entstandenen Unannehmlichkeiten.

2. resolved Jun 15, 2026, 07:49 AM UTC

   The system has been running stably for over an hour. We thank you for your patience and apologize again for any inconvenience caused. ************************ Das System läuft seit über einer Stunde stabil. Wir danken Ihnen für Ihre Geduld und entschuldigen uns nochmals für die entstandenen Unannehmlichkeiten.

Read the full incident report →

Started Jun 03, 2026, 07:43 AM UTC· resolved Jun 10, 2026, 07:19 AM UTC

1. investigating Jun 03, 2026, 07:43 AM UTC

   We’re currently investigating reports of a potential outage in one or more services in Pagero TMS. We are working on identifying the cause and impact on customers. The Mymo service are experiencing issues with generating shipments. We are currently investigating together with Mymo. We apologize for any inconvenience and will post new updates as soon as we learn anything more. If you have any questions, please contact our Support team

2. investigating Jun 03, 2026, 09:10 AM UTC

   The outages in Pagero Prepare has been resolved. This was mainly an issue of delays within prepare. The incident with Mymo is still ongoing and we are currently investigating together with Mymo. We apologize for any inconvenience and will post new updates as soon as we learn anything more. If you have any questions, please contact our Support team

3. investigating Jun 03, 2026, 10:16 AM UTC

   The incident with Mymo is still ongoing and we are currently investigating together with Mymo. We apologize for any inconvenience and will post new updates as soon as we learn anything more. If you have any questions, please contact our Support team

4. investigating Jun 03, 2026, 11:25 AM UTC

   The incident with Mymo is still ongoing and we are currently investigating together with Mymo. We apologize for any inconvenience and will post new updates as soon as we learn anything more. If you have any questions, please contact our Support team

5. identified Jun 03, 2026, 12:55 PM UTC

   We've found the root cause, and a fix is on it's way. We apologize for any inconvenience and will post new updates as soon as we learn anything more. If you have any questions, please contact our Support team

6. identified Jun 03, 2026, 02:18 PM UTC

   We've found the root cause, and a fix is on it's way. We apologize for any inconvenience and will post new updates as soon as we learn anything more. If you have any questions, please contact our Support team

7. monitoring Jun 04, 2026, 05:57 AM UTC

   A fix has been implemented and we are monitoring the results.

8. investigating Jun 05, 2026, 05:11 AM UTC

   The fix solved the overall problem, but some old shipment are still missing.

9. investigating Jun 05, 2026, 07:48 AM UTC

   We are still investigating this matter. All new shipments since the fix will be processed, but we are still looking into some missing ones.

10. monitoring Jun 05, 2026, 01:36 PM UTC

    All of the missing shipments has been identified and resent. We are still monitoring this matter.

11. resolved Jun 10, 2026, 07:19 AM UTC

    This incident has been resolved, affected components are back to normal.

Read the full incident report →

Started May 19, 2026, 01:45 PM UTC· resolved May 19, 2026, 01:56 PM UTC

1. identified May 19, 2026, 01:45 PM UTC

   We've been informed of a potential disturbance in the connection towards Posti Messaging Oy. It was identified around 14:37 CEST. Posti Messaging Oy identified the cause for this and they are working to fix it as soon as possible. The reported affected services are: -Invoice Sending. -EDI. -Invoice Receiving. They estimated that the services will be operational around 19.05.2026 17:30 CEST. We apologize for any inconvenience and will post new updates as soon as we learn anything more. If you have any questions, please contact our Support team

2. resolved May 19, 2026, 01:56 PM UTC

   The incident impacting connectivity with Posti Messaging Oy has been successfully resolved. The fix has been fully implemented, and the system has been closely monitored to confirm stability and normal performance. At this time, all services are operating as expected. Posti Messaging Oy are working on processing all the remaining documents. We sincerely apologize for any inconvenience this may have caused. If you have any questions, please contact our Support team

Read the full incident report →

Started May 06, 2026, 08:49 AM UTC· resolved May 06, 2026, 10:20 PM UTC

1. resolved May 06, 2026, 08:49 AM UTC

   Am 5. Mai 2026 verursachte ein DNS-Problem bei der DENIC, der zentralen Registrierungsstelle für die .de-Top-Level-Domain, weitreichende Verbindungsprobleme für Tausende deutscher Websites und Dienste. Die externe Verfügbarkeit unserer Services war zwischen dem 5. Mai um 21:50 Uhr MESZ und dem 6. Mai um 00:20 Uhr MESZ beeinträchtigt. In diesem Zeitraum kam es zu sporadischen Verbindungsproblemen für Kunden, die versuchten, auf unsere an .de-Domains gebundenen Services zuzugreifen. Die Ursache des Problems lag bei der DENIC-Registrierungsstelle und nicht bei Pagero oder dessen Serviceanbietern. Der Vorfall ist inzwischen behoben, und alle Services sind wieder regulär verfügbar und funktionsfähig. Wir entschuldigen uns für die entstandenen Unannehmlichkeiten. Mit freundlichen Grüßen Pagero Health Support *************************************************************************** On May 5th 2026, a DNS issue at DENIC, the central registry for the .de top-level domain, caused widespread connectivity problems for thousands of German websites and services. The external availability of our services was affected between May 5 21:50 CEST and May 6 00:20 CEST, causing intermittent connectivity problems for customers who tried to connect to our services tied to .de domains during that timeframe. The issue was caused by the DENIC registry, not by Pagero or its service providers. The incident has now been resolved and services are available and working as normal. We apologize for any inconvenience this might have caused. Kind regards Pagero Health Support

Read the full incident report →

Started Apr 24, 2026, 06:18 AM UTC· resolved Apr 24, 2026, 06:44 AM UTC

1. investigating Apr 24, 2026, 06:18 AM UTC

   We’re currently investigating reports of a potential outage in our E-Banking service in Pagero Online that was identified at 8:00 CEST. We are working on identifying the cause and impact on customers. We apologize for any inconvenience and will post new updates as soon as we learn anything more. If you have any questions, please contact our Support team

2. resolved Apr 24, 2026, 06:44 AM UTC

   The issue has now been resolved and services are available and working as normal. We apologize for any inconvenience this might have caused. If you have any questions, please contact our Support team

Read the full incident report →

Started Apr 20, 2026, 06:49 AM UTC· resolved Apr 20, 2026, 07:00 AM UTC

1. investigating Apr 20, 2026, 06:49 AM UTC

   We are currently investigating reports of a possible outage of Hospital Shops that was detected at 8:26 AM CET. We are working to identify the cause and the impact on customers. We apologize for any inconvenience and will post new updates as soon as we have more information. If you have any questions, please contact our Support team ************************* Wir untersuchen derzeit Berichte über einen möglichen Ausfall eines oder mehrerer Hospital Shops, der um 8:26 CET festgestellt wurde. Wir arbeiten daran, die Ursache und die Auswirkungen auf Kunden zu ermitteln. Wir entschuldigen uns für etwaige Unannehmlichkeiten und werden neue Updates veröffentlichen, sobald wir mehr erfahren. Wenn Sie Fragen haben, wenden Sie sich bitte an unser Support-Team

2. resolved Apr 20, 2026, 07:00 AM UTC

   The reason for the unavailability of our Hospital Shop has been identified and the issue has been fixed. All Hospital Shop services are working as usual again. If you have any questions, please contact our Support team ************************* Wir konnten die Ursache für den Ausfall unseres Hospital Shops identifizieren und beseitigen. Alle Funktionen des Hospital Shops arbeiten nun wieder normal. Wenn Sie Fragen haben, wenden Sie sich bitte an unser Support-Team

Read the full incident report →

Started Mar 25, 2026, 01:43 PM UTC· resolved Mar 31, 2026, 08:19 AM UTC

1. identified Mar 25, 2026, 01:43 PM UTC

   We are currently investigating an issue that began on March 3, 2026, affecting the submission of electronic invoices to FACe. During the submission process, FACe is returning Error Response 500, which is preventing the successful delivery of affected invoices. We are continuously investigating this issue together with our partner, in close coordination with FACe, in order to obtain confirmation of the root cause and the solution being implemented. We sincerely apologize for any inconvenience this issue may be causing and appreciate your patience while we work toward a resolution. If you have any questions, please contact our Support team

2. identified Mar 26, 2026, 09:34 AM UTC

   We continue to investigate the issue affecting the submission of electronic invoices to FACe. At this time, invoice submissions to FACe may still fail with Error Response 500. Our teams remain actively engaged with our partner and are working closely with FACe to confirm the root cause and validate the corrective actions being implemented. We will provide further updates as soon as more information becomes available. If you have any questions, please contact our Support team

3. identified Mar 26, 2026, 09:43 AM UTC

   We continue to investigate the issue affecting the submission of electronic invoices to FACe. If you have any questions, please contact our Support team

4. identified Mar 27, 2026, 06:25 AM UTC

   We are continuing to investigate the issue impacting electronic invoice submissions to FACe in collaboration with our partner. If you have any questions, please contact our Support team

5. monitoring Mar 27, 2026, 02:32 PM UTC

   We have been able to successfully resend most of the affected documents, and these are now processed as expected. We are closely monitoring the remaining documents that are still encountering the same error. In parallel, we remain in active contact with our partner to identify and confirm the root cause of this issue. Further updates will be shared as soon as new information becomes available. If you have any questions, please contact our Support team

6. monitoring Mar 30, 2026, 06:25 AM UTC

   We have not detected any additional documents being stopped with this error. The majority of the affected documents have now been successfully resent and processed as expected. For the small number of documents that remain stopped, we have proactively contacted the respective senders to ensure they are aware of the situation and of the viable solution available to proceed. We continue to monitor the situation closely and remain in contact with our partner to confirm the root cause. We will share further updates should there be any relevant developments. If you have any questions, please contact our Support team

7. resolved Mar 31, 2026, 08:19 AM UTC

   Following a monitoring period of the last couple of days, we can confirm that no further documents have been affected and that the submission of documents to FACe is now working as expected. Thank you for your patience while we investigated this matter. If you have any questions, please contact our Support team

Read the full incident report →

Started Mar 06, 2026, 09:40 AM UTC· resolved Mar 06, 2026, 09:44 PM UTC

1. investigating Mar 06, 2026, 09:40 AM UTC

   All parts of our system are currently unavailable. We are investigating the root cause.

2. investigating Mar 06, 2026, 09:53 AM UTC

   The system is available again. Logging in could still take a while longer. We will continue to monitor the situation.

3. resolved Mar 06, 2026, 09:44 PM UTC

   The incident has been resolved.

Read the full incident report →

Started Mar 01, 2026, 05:24 AM UTC· resolved Mar 01, 2026, 08:31 AM UTC

1. investigating Mar 01, 2026, 05:24 AM UTC

   We want to inform you that we are currently experiencing a service outage. Our team is aware of the issue and is actively investigating the cause to resolve it as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time. We will keep you updated on our progress and notify you as soon as the issue is resolved. Thank you.

2. resolved Mar 01, 2026, 08:31 AM UTC

   The issue has been resolved and all services are now available and operating normally. We apologize for any inconvenience this may have caused. If you have any questions, please contact our Support team: https://www.thomsonreuters.com/en-us/help/pagero

Read the full incident report →

Started Feb 26, 2026, 07:38 AM UTC· resolved Feb 26, 2026, 01:18 PM UTC

1. identified Feb 26, 2026, 07:38 AM UTC

   Unfortunately there is a malfunction in the Health OCR Order transmission since 08.00 AM CE(S)T. We are working hard to find a solution and will inform you as soon as possible as soon as the problem is solved or there is new information about the current status. If you have any questions, please contact our Support team ************************** leider besteht seit 08:00 CET ein Störung in der Health OCR Order Auftragsübermittlung. Wir arbeiten mit Hochdruck an einer Lösung und werden Sie schnellstmöglich informieren, sobald die Störung behoben ist oder es neue Informationen zum aktuellen Stand gibt. Wenn Sie Fragen haben, wenden Sie sich bitte an unser Support-Team

2. monitoring Feb 26, 2026, 08:17 AM UTC

   ✓ Current Status: All OCR orders received today from 08:52 AM CET onwards are being processed normally again. ⏳ In Progress: Orders from yesterday, February 25, 2026, approx. 4:30 PM until today 08:52 AM cannot be processed yet. We will keep you updated on the progress. ***************************** ✓ Aktueller Status: Alle OCR-Bestellungen, die heute ab 08:52 Uhr CET eingelaufen sind, werden wieder normal verarbeitet. ⏳ In Bearbeitung: Eingelaufene Bestellungen von gestern, dem 25.02.2026 ca. 16:30 Uhr bis heute 08:52 Uhr können im Moment noch nicht verarbeitet werden. Wir halten Sie über den Fortschritt auf dem Laufenden.

3. monitoring Feb 26, 2026, 11:02 AM UTC

   We are continuing to monitor for any further issues.

4. monitoring Feb 26, 2026, 11:03 AM UTC

   ⏳ In Progress: The affected orders (Feb 25, 4:30 PM - Feb 26, 8:52 AM CET) are currently being reprocessed. Expected completion: Today, approx. 3:00 PM CET. ********************* ⏳ In Bearbeitung: Die betroffenen Bestellungen (25.02., 16:30 Uhr - 26.02., 08:52 Uhr) werden derzeit nachverarbeitet. Voraussichtliche Fertigstellung: Heute, ca. 15:00 Uhr CET.

5. resolved Feb 26, 2026, 01:18 PM UTC

   ✓ Resolved: All affected orders have been successfully processed and transmitted by 1:55 PM CET. ***************************** ✓ Behoben: Alle betroffenen Bestellungen wurden bis 13:55 Uhr CET erfolgreich verarbeitet und übertragen.

Read the full incident report →

Started Feb 20, 2026, 05:00 AM UTC· resolved Feb 20, 2026, 07:33 PM UTC

1. resolved Feb 20, 2026, 09:24 AM UTC

   Our Health SFTP server was down yesterday from 06:00 to 08:33PM CET. If any errors occurred in your data transmissions during this time, please repeat them if necessary! Affected host addresses: ftp.hbsolutions.de sftp.hbsolutions.de ftp2.hbsolutions.de If you have any questions, please contact our Support team ************************** Unser Health SFTP Server war gestern in der Zeit von 18:00 bis 20:33 CET ausgefallen. Sollten in dieser Zeit Fehler in Ihren Datenübertragungen aufgetreten sein, wiederholen Sie diese bitte gegebenenfalls! Betroffene Host-Adressen: ftp.hbsolutions.de sftp.hbsolutions.de ftp2.hbsolutions.de Wenn Sie Fragen haben, wenden Sie sich bitte an unser Support-Team

Read the full incident report →

Started Feb 16, 2026, 08:28 AM UTC· resolved Feb 16, 2026, 12:07 PM UTC

1. investigating Feb 16, 2026, 08:28 AM UTC

   We’re currently investigating reports of potential document processing delays in one or more services in Pagero Online that was identified at 8:30 CET. This is resulting in documents currently taking a long time to be processed and delivered. We apologize for any inconvenience and will post new updates as soon as we learn anything more. If you have any questions, please contact our Support team

2. identified Feb 16, 2026, 09:40 AM UTC

   We have identified and resolved the cause of the issue. We’re still working on processing a large queue of documents currently in processing and as such there are still delays for documents being delivered. We apologize for any inconvenience and will post new updates as soon as we learn anything more. If you have any questions, please contact our Support team

3. resolved Feb 16, 2026, 12:07 PM UTC

   The issue has now been resolved and services are available and working as normal. We apologize for any inconvenience this might have caused. If you have any questions, please contact our Support team

Read the full incident report →