Pagero Outage History

Pagero is up right now

Pagero had 35 outages in the last 2 years totaling 1365h 49m of downtime — averaging 1.4 incidents per month.

There were 35 Pagero outages since June 23, 2025 totaling 1365h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pagero.com

Minor May 19, 2026

Pagero Online - Disturbances in the connection towards Posti Messaging Oy

Detected by Pingoru
May 19, 2026, 01:45 PM UTC
Resolved
May 19, 2026, 01:56 PM UTC
Duration
11m
Affected: Pagero Online
Timeline · 2 updates
  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 →

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 →

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 →

Major January 21, 2026

Ongoing incident with webservices

Detected by Pingoru
Jan 21, 2026, 12:55 PM UTC
Resolved
Feb 03, 2026, 01:50 PM UTC
Duration
13d
Affected: Pagero TMS
Timeline · 5 updates
  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 →

Notice December 19, 2025

Partial outage in connections to Health Center / Teilweise Verbindungsstörung zum Health Center

Detected by Pingoru
Dec 19, 2025, 04:10 PM UTC
Resolved
Dec 19, 2025, 04:10 PM UTC
Duration
—
Affected: Health Center/Health Mobile
Timeline · 1 update
  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 →

Minor November 27, 2025

Statuses are not being processed

Detected by Pingoru
Nov 27, 2025, 09:29 AM UTC
Resolved
Dec 02, 2025, 08:17 AM UTC
Duration
4d 22h
Affected: Pagero TMS
Timeline · 4 updates
  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 →

Notice November 20, 2025

Issue with Received Documents Tab

Detected by Pingoru
Nov 20, 2025, 09:42 AM UTC
Resolved
Nov 20, 2025, 12:53 PM UTC
Duration
3h 10m
Affected: Pagero Online
Timeline · 3 updates
  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 →

Minor November 20, 2025

Disturbances in the connection towards FACe (Spanish e-invoicing entry point)

Detected by Pingoru
Nov 20, 2025, 09:30 AM UTC
Resolved
Nov 24, 2025, 08:34 AM UTC
Duration
3d 23h
Affected: Pagero Online
Timeline · 4 updates
  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 →

Major November 7, 2025

Malfunction in Health OCR Order / Störung in der Health OCR Order

Detected by Pingoru
Nov 07, 2025, 12:19 PM UTC
Resolved
Nov 10, 2025, 09:20 AM UTC
Duration
2d 21h
Affected: Health OCR Order
Timeline · 4 updates
  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 →

Major November 7, 2025

Pagero Online - Potential outage

Detected by Pingoru
Nov 07, 2025, 12:04 PM UTC
Resolved
Nov 11, 2025, 07:19 AM UTC
Duration
3d 19h
Affected: Pagero Online
Timeline · 4 updates
  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 →

Notice October 30, 2025

Delay in processing documents on LHDN due to site Maintenance

Detected by Pingoru
Oct 30, 2025, 06:21 PM UTC
Resolved
Oct 31, 2025, 05:25 AM UTC
Duration
11h 3m
Affected: Pagero Online
Timeline · 2 updates
  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 →

Notice October 22, 2025

Pagero Online - Possible error in documents

Detected by Pingoru
Oct 22, 2025, 09:12 AM UTC
Resolved
Oct 22, 2025, 09:12 AM UTC
Duration
—
Affected: Pagero Online
Timeline · 1 update
  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 →

Notice October 20, 2025

Temporary Phone Support Unavailability

Detected by Pingoru
Oct 20, 2025, 03:24 PM UTC
Resolved
Oct 21, 2025, 12:57 AM UTC
Duration
9h 32m
Affected: Pagero Online
Timeline · 4 updates
  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 →

Notice October 20, 2025

Pagero Online - Duplicate reconciliation files in our E-banking service

Detected by Pingoru
Oct 20, 2025, 09:56 AM UTC
Resolved
Oct 20, 2025, 01:18 PM UTC
Duration
3h 21m
Affected: Pagero Online
Timeline · 3 updates
  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 →

Notice October 20, 2025

Pagero Online - Document Retrieval Delays

Detected by Pingoru
Oct 20, 2025, 05:05 AM UTC
Resolved
Oct 20, 2025, 03:49 PM UTC
Duration
10h 44m
Affected: Pagero Online
Timeline · 4 updates
  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 →