Pagero Outage History

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 →

Started Feb 09, 2026, 10:31 AM UTC· resolved Feb 09, 2026, 10:59 AM UTC

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 →

Started Jan 21, 2026, 12:55 PM UTC· resolved Feb 03, 2026, 01:50 PM UTC

1. investigating Jan 21, 2026, 12:55 PM UTC

   We are currently having issues with our web services, which is affect incoming files, and the Prepare menu. We are also investigating which other components might be affected.

2. monitoring Jan 21, 2026, 01:28 PM UTC

   Our network provider identified an issue, and their servers needed to be restarted. All services seem to be back to normal, but we will keep monitoring the situation.

3. monitoring Jan 21, 2026, 03:08 PM UTC

   All parts of our service are up and running, but we will continue to monitor to make sure everything is working as intended.

4. monitoring Jan 22, 2026, 08:47 AM UTC

   All systems are back to normal.

5. resolved Feb 03, 2026, 01:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 19, 2025, 01:20 PM UTC· resolved Dec 19, 2025, 02:05 PM UTC

1. resolved Dec 19, 2025, 04:10 PM UTC

   Due to an outage in our Health VPN-Services some customers were unable to reach our Health Center between 2:20 PM and 3:05 PM CET. If any documents on your side were not transferred during the above mentioned time, please resend them to us. We apologize for any inconvenience this may have caused. If you have any questions, please contact our Support team ************************************ Aufgrund einer Störung in unseren Health-VPN-Diensten konnten einige Kunden unser Health Center zwischen 14:20 Uhr und 15:05 Uhr MEZ nicht erreichen. Falls während des oben genannten Zeitraums auf Ihrer Seite Dokumente nicht übertragen wurden, senden Sie diese bitte erneut an uns. Bitte entschuldigen Sie dadurch ggfs. entstandenen Unannehmlichkeiten. Wenn Sie Fragen haben, wenden Sie sich bitte an unser Support-Team

Read the full incident report →

Started Nov 27, 2025, 09:29 AM UTC· resolved Dec 02, 2025, 08:17 AM UTC

1. identified Nov 27, 2025, 09:29 AM UTC

   We have been unable to process any statuses since the release on the 17th of November. The root cause has been found, and we are working on a fix at the moment.

2. identified Nov 27, 2025, 01:55 PM UTC

   All statuses in queue has been processed manually, but we are still working with the root cause.

3. identified Nov 28, 2025, 12:23 PM UTC

   We have not yet found a fix, but found a way to handle all statuses manually until then.

4. resolved Dec 02, 2025, 08:17 AM UTC

   The main issue has been resolved, and the status-flow is up and functional.

Read the full incident report →

Started Nov 20, 2025, 09:42 AM UTC· resolved Nov 20, 2025, 12:53 PM UTC

1. investigating Nov 20, 2025, 09:42 AM UTC

   We are currently investigating an issue affecting the Received Documents tab in Pagero Online. Our team is working to identify the root cause and will provide updates as soon as possible. If you have any questions, please contact our Support team

2. monitoring Nov 20, 2025, 11:11 AM UTC

   A fix has been implemented and we are monitoring the results. If you have any questions, please contact our Support team

3. resolved Nov 20, 2025, 12:53 PM UTC

   The issue affecting the Received Documents tab in Pagero Online has now been resolved. Our team identified the root cause and implemented the necessary fix to prevent it from recurring. Thank you for your patience while we worked on this. If you experience any further difficulties or have additional questions, please don’t hesitate to reach out. If you have any questions, please contact our Support team

Read the full incident report →

Started Nov 20, 2025, 09:30 AM UTC· resolved Nov 24, 2025, 08:34 AM UTC

1. identified Nov 20, 2025, 09:30 AM UTC

   We’re currently investigating reports of a potential disturbance in the connection towards FACe (Spanish e-invoicing entry point). It was identified around yesterday 22:29 CET. We are working on identifying the cause and impact on customers with our Partner. 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 Nov 20, 2025, 09:41 AM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Nov 24, 2025, 07:08 AM UTC

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

4. resolved Nov 24, 2025, 08:34 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 17, 2025, 09:11 AM UTC· resolved Dec 02, 2025, 08:20 AM UTC

1. investigating Nov 17, 2025, 09:11 AM UTC

   Right now, we are having issues with routing, and the system might behave unexpectedly. We will deploy a patch around 12:00, which might log out any users who are logged in during this period.

2. investigating Nov 17, 2025, 11:16 AM UTC

   We will deploy a patch at 12:25, which will log active users out of TMS. There will be a downtime of approximately 10-15 minutes. Sorry for any inconvenience.

3. investigating Nov 17, 2025, 11:24 AM UTC

   A patch has been deployed in our PROD-environment.

4. investigating Nov 17, 2025, 11:49 AM UTC

   We are continuing to investigate this issue.

5. monitoring Nov 17, 2025, 12:20 PM UTC

   A lunch-release was sent, fixing the issue with multiple CSs not getting consolidated. Now, the work is to find the TSes, and update them, cancelling all but one and reroute the CSes to hit the same TS. We will update you with the instructions for this.

6. investigating Nov 17, 2025, 03:05 PM UTC

   Load list and Pre-defined reports not working as indended. Error message is seen when trying to use them. The Routing issues is fixed, and should work as intended.

7. identified Nov 18, 2025, 06:49 AM UTC

   The issues with routing has been solved. Pre-defined report has been fixed. Still investigating loadlists and slow processing of shipments.

8. identified Nov 18, 2025, 08:47 AM UTC

   We believe we've found the root cause of the loadlists issues. A patch will be delivered in about 30 minutes.

9. monitoring Nov 18, 2025, 09:34 AM UTC

   The fix has been deployed to PROD, and we could find new loadlists. We are monitoring the situation for now.

10. monitoring Nov 18, 2025, 11:14 AM UTC

    All loadlists have been processed. We are monitoring this for the moment.

11. identified Nov 24, 2025, 12:24 PM UTC

    We have released a patch for slow processing of invoices and shipments. The patch brought the time for processing down, but not enough. This is still under investigation.

12. identified Nov 25, 2025, 03:00 PM UTC

    This issue is still under investigation.

13. investigating Nov 26, 2025, 01:17 PM UTC

    This issue is still being investigated.

14. identified Nov 27, 2025, 01:56 PM UTC

    There has been small patches deployed during the week, which has had some improvements on processing speed. We are still working on further fixes.

15. identified Nov 28, 2025, 12:23 PM UTC

    This issue is still being investigated.

16. resolved Dec 02, 2025, 08:20 AM UTC

    Billing and transfer of shipments is back at a normal pace.

Read the full incident report →

Started Nov 07, 2025, 12:19 PM UTC· resolved Nov 10, 2025, 09:20 AM UTC

1. investigating Nov 07, 2025, 12:19 PM UTC

   Unfortunately there is a malfunction in the Health OCR Order transmission since 13:00 CET. 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 13:00 CET eine 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. identified Nov 07, 2025, 01:37 PM UTC

   The root cause of the incident has been identified and a fix is being deployed.

3. monitoring Nov 07, 2025, 09:09 PM UTC

   The issue with the Pagero Health OCR processing (Order & Invoice) has been resolved. Our staff will start processing the backlog of orders as a top priority from Monday morning. We anticipate this will be completed by noon at the latest. We apologize once again for any inconvenience this may have caused. If you have any questions, please contact our Support team ********************************* Die Störung in der Pagero Health OCR Verarbeitung (Order & Invoice) wurde gelöst. Unsere Mitarbeiter werden ab Montagmorgen mit höchster Priorität an der Verarbeitung aufgestauter Bestellungen beginnen. Wir rechnen damit, dass bis spätestens zum Mittag erledigt sein wird. Wir möchten uns noch einmal für entstandende Unannehmlichkeiten entschuldigen. Wenn Sie Fragen haben, wenden Sie sich bitte an unser Support-Team

4. resolved Nov 10, 2025, 09:20 AM UTC

   The orders affected by the disruption on Friday have now all been processed. Pagero Health OCR processing (Order & Invoice) is functioning as usual again. We would like to once again apologize for any inconvenience caused. If you have any questions, please contact our Support team ************************** Die von der Störung betroffenen Bestellungen vom Freitag sind nun ebenfalls alle verarbeitet. Die Pagero Health OCR Verarbeitung (Order & Invoice) funktioniert wieder wie gewohnt. Wir möchten uns noch einmal für entstandene Unannehmlichkeiten entschuldigen. Wenn Sie Fragen haben, wenden Sie sich bitte an unser Support-Team

Read the full incident report →

Started Nov 07, 2025, 12:04 PM UTC· resolved Nov 11, 2025, 07:19 AM UTC

1. investigating Nov 07, 2025, 12:04 PM UTC

   We’re currently investigating reports of a potential outage in one or more services in Pagero Online that was identified at 13:00 CET. 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 Nov 07, 2025, 01:09 PM UTC

   The root cause of the incident has been identified and a fix is being deployed.

3. monitoring Nov 07, 2025, 06:39 PM UTC

   All services are working as expected, although they will be all monitored during the weekend to ensure everything is working correctly. We apologize for any inconvenience this may have caused. If you have any questions, please contact our Support team

4. resolved Nov 11, 2025, 07:19 AM UTC

   After close monitoring, we can confirm that the issue has now been resolved. 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 Oct 30, 2025, 06:21 PM UTC· resolved Oct 31, 2025, 05:25 AM UTC

1. investigating Oct 30, 2025, 06:21 PM UTC

   Dear Customer, The Malaysian flow is undergoing an unannounced maintenance by the correspondent tax authority and some documents might be affected until this maintenance is finished. We're monitoring this closely and will share updates as we have them. Thank you for your patience and understanding.

2. resolved Oct 31, 2025, 05:25 AM UTC

   This maintenance has been resolved.

Read the full incident report →

Started Oct 22, 2025, 09:12 AM UTC· resolved Oct 22, 2025, 09:12 AM UTC

1. resolved Oct 22, 2025, 09:12 AM UTC

   We discovered Oct 21, 2025 02:28:12 UTC that the StaticMapping service was incorrectly applying scripts to the wrong document types. This caused some documents to fail and others to be processed incorrectly. The issue only affected Pagero customers with multiple recipients and active enrichment scripts for different document types. A stable release was deployed at Oct 21, 12:39:41 UTC and the previously failed documents have been successfully processed. We're still investigating to find any documents that may have been affected by incorrect mappings. We apologize for the inconvenience and will share updates as soon as we have more information. If you have any questions, please contact our Support team

Read the full incident report →

Started Oct 20, 2025, 03:24 PM UTC· resolved Oct 21, 2025, 12:57 AM UTC

1. identified Oct 20, 2025, 03:24 PM UTC

   We’re currently experiencing an issue with our phone service provider that is impacting our ability to receive incoming calls. All other support channels — including web case creation, email, and live chat — remain fully operational. Our provider is actively working to resolve the issue, and our internal teams are implementing additional measures to maintain service stability. We apologize for any inconvenience and appreciate your patience while we work toward a full resolution.

2. identified Oct 20, 2025, 03:39 PM UTC

   We’ve identified that the issue affecting our phone services is related to a broader global AWS outage. This disruption is causing issues with inbound calls. The impacted platform continues to work toward resolution. All other support channels — including web case creation, email, and live chat — remain fully available. We’re closely monitoring the situation and will continue to provide updates as more information becomes available. Thank you for your continued patience.

3. monitoring Oct 20, 2025, 08:30 PM UTC

   We're actively investigating an issue that affected our phone services as part of a broader global AWS outage. Inbound calls are working again, but you may still experience occasional interruptions while we finalize a fix. We're working closely with our platform provider to ensure stability and a full resolution. All other support channels, web case creation, email, and live chat, are operating normally. We're monitoring this closely and will share updates as we have them. Thank you for your patience and understanding.

4. resolved Oct 21, 2025, 12:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 09:56 AM UTC· resolved Oct 20, 2025, 01:18 PM UTC

1. investigating Oct 20, 2025, 09:56 AM UTC

   We’re currently investigating reports of duplicate reconciliation files received by our customers for our E-banking service in Pagero Online. 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 Oct 20, 2025, 11:12 AM UTC

   We have identified that the duplicate reconciliation files is limited to files from SEB and transactions with execution date 2025-10-17. The duplicates will either show up as if the same transaction would have been executed several times when checking the reconciliation file(s) or as separate identical reconciliation file(s). Please note that it is only the reporting that is affected, the actual transactions has NOT been executed incorrectly (multiple times). We are still investigating the cause of this issue. If you have any questions, please contact our Support team

3. resolved Oct 20, 2025, 01:18 PM UTC

   We have identified the root cause of the duplicate reconciliation files issue. The problem occurred when our services were restarted following the infrastructure incident reported previously in https://status.pagero.com/incidents/fndbwr5xcn5c. During the restart, the same files were processed multiple times before the system had fully synchronized, resulting in duplicate reconciliation files appearing in the service. The duplicates will either show up as if the same transaction would have been executed several times when checking the reconciliation file(s) or as separate identical reconciliation file(s). Please note that it is only the reporting that is affected - the actual transactions has NOT been executed incorrectly (multiple times). If you have any questions, please contact our Support team

Read the full incident report →

Started Oct 20, 2025, 05:05 AM UTC· resolved Oct 20, 2025, 03:49 PM UTC

1. investigating Oct 20, 2025, 05:05 AM UTC

   We are currently investigating some delays when retrieving documents through both the Document API and the Document Web interface. This means that documents might take longer than usual to appear in the new Pagero Online platform and via API queries. Please rest assured that document processing is continuing as normal, and all documents will eventually become available. We appreciate your patience and understanding while we work to resolve this issue.

2. investigating Oct 20, 2025, 08:38 AM UTC

   We are continuing to investigate the delays affecting document retrieval via both the Document API and the Document Web interface. We understand the importance of timely access to your documents and appreciate your continued patience. Our teams are actively working to resolve the issue and will provide further updates as soon as more information becomes available. If you have any questions, please contact our Support team

3. investigating Oct 20, 2025, 01:03 PM UTC

   We are currently still experiencing delays in document retrieval through both the Document API and the Document Web interface. The issue has been identified as server-related, and our technical teams are actively working to resolve it. In the meantime, we have implemented a temporary mitigation to ensure that documents are processed and made available within a reasonable timeframe. While delays may persist, document processing continues uninterrupted. We appreciate your continued patience. Please do not hesitate on contact us on Support team.

4. resolved Oct 20, 2025, 03:49 PM UTC

   We are pleased to report that the delays in document retrieval through both the Document API and Document Web interface have been fully resolved. Our technical teams have addressed the server-related issue, and document processing is now operating as expected. Thank you for your patience and understanding while we worked to resolve this matter. If you experience any further issues, please contact us via Support.

Read the full incident report →

Started Oct 18, 2025, 10:30 AM UTC· resolved Oct 18, 2025, 01:13 PM UTC

1. investigating Oct 18, 2025, 10:30 AM UTC

   We are aware of an ongoing issue impacting the Pagero SFTP server. Our dedicated technical teams are working with our infrastructure partners to identify the cause and implement a solution as swiftly as possible. We sincerely apologize for any inconvenience this may cause and appreciate your understanding during this time. Further updates will be provided as soon as new information becomes available. If you have any questions, please contact our Support team

2. monitoring Oct 18, 2025, 10:50 AM UTC

   We are pleased to inform you that the Pagero sFTP server connection is now functioning again. Our teams will continue to closely monitor the service to ensure stability and prevent any further disruptions. Thank you for your patience and understanding throughout this incident. We will provide additional updates if necessary. If you have any questions, please contact our Support team

3. resolved Oct 18, 2025, 01:13 PM UTC

   The incident affecting some Pagero Online services was caused by a network issue, which resulted in delays in document delivery for some customers. Our Support team has retriggered all impacted documents, and they have been correctly processed. The issue is now resolved, and all services are operating as expected.

Read the full incident report →

Started Oct 16, 2025, 06:25 AM UTC· resolved Oct 16, 2025, 12:41 PM UTC

1. investigating Oct 16, 2025, 06:25 AM UTC

   We are currently investigating delays in document delivery in Pagero Online, first identified at 4:25 AM CEST. Our team is working to determine the cause of the issue and assess its impact. 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 Oct 16, 2025, 12:41 PM UTC

   The delays in document delivery in Pagero Online have been resolved. Our investigation identified the root cause as a bug in a database that led to system slowness. All services are now operating as expected. We are currently testing a permanent fix and will deploy it shortly to prevent recurrence. Thank you for your patience and understanding. If you have any questions, please contact our Support team

3. resolved Oct 16, 2025, 12:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 11, 2025, 07:49 AM UTC· resolved Sep 11, 2025, 10:22 AM UTC

1. investigating Sep 11, 2025, 07:49 AM UTC

   Unfortunately there is a malfunction in the Pagero Health OCR processing (Order & Invoice) since today, 7:30 AM (CET). 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 heute, 7:30 Uhr (CET) ein Störung in der Pagero Health OCR Verarbeitung (Order & Invoice). 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. resolved Sep 11, 2025, 10:22 AM UTC

   The issue in the Pagero Health OCR processing (Order & Invoice) has been resolved. Our staff are working with the highest priority on processing your purchase orders. However, it will still take some time until the backlog is fully cleared. If you have any questions, please contact our Support team ************************** Die Störung in der Pagero Health OCR Verarbeitung (Order & Invoice) wurde gelöst. Unsere Mitarbeiter arbeiten mit höchster Priorität an der Verarbeitung Ihrer Bestellungen. Es wird allerdings noch etwas dauern bis der Rückstau vollständig aufgelöst ist. Wenn Sie Fragen haben, wenden Sie sich bitte an unser Support-Team

Read the full incident report →

Started Aug 28, 2025, 08:13 AM UTC· resolved Aug 28, 2025, 11:08 AM UTC

1. investigating Aug 28, 2025, 08:13 AM UTC

   We have received information the E-Invoice and E-Way Bill services are currently unavailable due to an unexpected outage from NIC (National Informatic Centre). This issue is affecting all service providers nationwide in India. We, along with the partner, are closely monitoring the situation. We will promptly update you as soon as the services are restored. This is impacting the Indian flow only. If you have any questions, please contact our Support team

2. resolved Aug 28, 2025, 11:08 AM UTC

   The outage at the National Informatics Centre (NIC) has been resolved, and all services have been fully restored. Our monitoring indicates that operations are proceeding as expected. We apologize for any inconvenience this may have caused. If you have any questions, please contact our Support team

Read the full incident report →

Started Aug 07, 2025, 11:30 AM UTC· resolved Aug 08, 2025, 12:01 PM UTC

1. investigating Aug 07, 2025, 11:30 AM UTC

   We’re currently investigating reports of delays in document processing in documents sent from Pagero Online to operator Posti Messaging. 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. monitoring Aug 08, 2025, 05:09 AM UTC

   A fix has been implemented and we expect documents to now be processed as normal. We are actively monitoring the document flow to ensure everything is functioning correctly.

3. resolved Aug 08, 2025, 12:01 PM UTC

   The delay in document processing has been resolved.

Read the full incident report →