Pagero Outage History

Pagero is up right now

There were 10 Pagero outages since February 6, 2026 totaling 281h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pagero.com

Notice April 24, 2026

Pagero Online - Potential outage for E-banking service

Detected by Pingoru
Apr 24, 2026, 06:18 AM UTC
Resolved
Apr 24, 2026, 06:44 AM UTC
Duration
26m
Affected: Pagero Online
Timeline · 2 updates
  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 →

Critical April 20, 2026

Malfunction in Hospital Shop / Störung in den Hospital Shops

Detected by Pingoru
Apr 20, 2026, 06:49 AM UTC
Resolved
Apr 20, 2026, 07:00 AM UTC
Duration
11m
Affected: Hospital Shop
Timeline · 2 updates
  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 →

Minor March 25, 2026

Incident affecting invoice submissions to FACe (Spanish e-invoicing entry point)

Detected by Pingoru
Mar 25, 2026, 01:43 PM UTC
Resolved
Mar 31, 2026, 08:19 AM UTC
Duration
5d 18h
Affected: Pagero Online
Timeline · 7 updates
  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 →

Critical March 6, 2026

Pagero TMS unreachable

Detected by Pingoru
Mar 06, 2026, 09:40 AM UTC
Resolved
Mar 06, 2026, 09:44 PM UTC
Duration
12h 4m
Affected: Pagero TMS
Timeline · 3 updates
  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 →

Critical March 1, 2026

Log in issue Pagero Online

Detected by Pingoru
Mar 01, 2026, 05:24 AM UTC
Resolved
Mar 01, 2026, 08:31 AM UTC
Duration
3h 7m
Affected: Pagero Online
Timeline · 2 updates
  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 →

Minor February 26, 2026

Malfunction in Health Solutions HBS OCR Order Service / Störung im Service Health Solutions HBS OCR Order

Detected by Pingoru
Feb 26, 2026, 07:38 AM UTC
Resolved
Feb 26, 2026, 01:18 PM UTC
Duration
5h 40m
Affected: Health OCR Order
Timeline · 5 updates
  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 →

Notice February 20, 2026

Malfunction in Health SFTP

Detected by Pingoru
Feb 20, 2026, 09:24 AM UTC
Resolved
Feb 20, 2026, 09:24 AM UTC
Duration
—
Affected: Health Center AS2
Timeline · 1 update
  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 →

Minor February 16, 2026

Pagero Online - Delays in document processing

Detected by Pingoru
Feb 16, 2026, 08:28 AM UTC
Resolved
Feb 16, 2026, 12:07 PM UTC
Duration
3h 39m
Affected: Pagero Online
Timeline · 3 updates
  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 →

Minor February 9, 2026

Pagero Online - Degraded Performance on SFTP Server (ftp.pageroonline.com)

Detected by Pingoru
Feb 09, 2026, 10:31 AM UTC
Resolved
Feb 09, 2026, 10:59 AM UTC
Duration
27m
Affected: Pagero Online
Timeline · 2 updates
  1. identified Feb 09, 2026, 10:31 AM UTC

    We’re currently investigating reports of a potential outage for our Pagero SFTP-server (ftp.pageroonline.com) in Pagero Online that was identified at 10:00 CEST. At this time, the issue appears to impact file uploads (write operations) to the SFTP server, and we are seeing failures when attempting to write files. 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 Feb 09, 2026, 10:59 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. The root cause was a storage-related issue on the SFTP server, which has now been addressed. If you have any questions, please contact our Support team

Read the full incident report →

Minor February 6, 2026

Disturbances in the connection from KSeF

Detected by Pingoru
Feb 06, 2026, 09:40 AM UTC
Resolved
Feb 11, 2026, 07:01 AM UTC
Duration
4d 21h
Affected: Pagero Online
Timeline · 6 updates
  1. investigating Feb 06, 2026, 09:40 AM UTC

    We’re currently investigating reports of a potential disturbance in the connection from KSeF. It was identified around 2026-02-05 at 9:05 AM (CET), causing slowness in the exporting documents. 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. identified Feb 06, 2026, 03:25 PM UTC

    We have identified the root cause of the incident and are implementing a solution as soon as possible. We apologize for any inconvenience and will provide updates as they become available. If you have any questions, please contact our Support team

  3. monitoring Feb 07, 2026, 11:25 AM UTC

    Our specialized team has implemented a fix to this issue, but we will monitor it during the weekend to ensure everything is working as expected. We truly apologize for any inconvenience this may have caused, and we will notify accordingly once we confirm everything is working correctly. If you have any questions, please contact our Support team

  4. monitoring Feb 09, 2026, 08:41 AM UTC

    We are still monitoring the situation closely to ensure continued stability and to confirm that no further impact occurs. The underlying issue has been resolved, and we are currently working on fetching all pending invoices. We expect this process to be completed during the course of the day. We apologize for any inconvenience this incident may have caused and appreciate your patience. If you have any questions, please contact our .

  5. monitoring Feb 10, 2026, 08:52 AM UTC

    We have not observed any additional impact since the fix was applied. Our team is actively completing the recovery process by retrieving any remaining pending invoices. We appreciate your understanding while this work is finalized and apologize for any disruption this may have caused. If you have any questions, please contact our Support team

  6. resolved Feb 11, 2026, 07:01 AM UTC

    The incident impacting connectivity with KSeF 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. 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 →

Looking to track Pagero downtime and outages?

Pingoru polls Pagero's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Pagero reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Pagero alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Pagero for free

5 free monitors · No credit card required