
Pagero Service Status
Real-time updates of Pagero Service issues and outages
Pagero Service status is Operational
Pagero Service Pagero Online
Active Incidents
No active incidents
Recently Resolved Incidents
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
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.
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.
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
Pagero Service Outage Survival Guide
Pagero Service Components
Pagero Service Pagero Support Center
Pagero Service Pagero Online
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
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
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.
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.