Pingen Outage History
Pingen is up right nowPingoru has recorded 12 incidents for Pingen: 4 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 1 | 1 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 1 | 4 of 744 (1%) |
| November 2026 | 0 | 0 of 47 (0%) |
Incidents, newest first
Major October 21, 2026 Important security updates due to worldwide PHP vulnerability 4h 10m API, Web Application, Payments & Billing
Started Oct 21, 2026, 12:00 PM UTC· resolved Oct 21, 2026, 04:10 PM UTC
- resolved Oct 22, 2026, 07:09 AM UTC
The yesterday announced PHP vulnerability CVE-2026-109618 and CVE-2026-109619, which affected part of our systems, was monitored throughout the day. As details about the vulnerability were not publicly available until late in the day, we inspected traffic for suspicious activities. At approximately 18:00 CEST yesterday, 21st of October, the fixed PHP version images were released, and by 18:10 all our systems were patched. Our investigations have concluded that no fraudulent activity took place on our platform, and have contracted an external security service to verify our findings, as well as work with us to monitor the development of this worldwide issue.
Major July 21, 2026 Supplier experiencing storage related issues 36m API, Web Application
Started Jul 21, 2026, 09:01 AM UTC· resolved Jul 21, 2026, 09:37 AM UTC
- investigating Jul 21, 2026, 09:01 AM UTC
Our Storage supplier is experiencing an outage. This has a system wide effect for processing entities in pingen. We are monitoring the situation and will inform accordingly.
- investigating Jul 21, 2026, 09:24 AM UTC
Our supplier informs us that all services are restored. We will monitor the situation to confirm that all is operation again. We apologise for the inconvenience this outage caused.
- resolved Jul 21, 2026, 09:37 AM UTC
The Systems have been stable for the past time and we are closing this issue.
Major February 3, 2026 Intermittent unavailability of the API & UI 1h 9m API, Web Application
Started Feb 03, 2026, 12:09 PM UTC· resolved Feb 03, 2026, 01:19 PM UTC
- investigating Feb 03, 2026, 12:09 PM UTC
Due to still unknown reasons, for short periods of time the API and UI are not reachable. Integrations are not affected. We are investigating and shutting down affected API instances and spawning new ones as it happens until the root cause is found.
- monitoring Feb 03, 2026, 12:18 PM UTC
We've fixed the core issue, and are waiting for things to recover.
- resolved Feb 03, 2026, 01:19 PM UTC
We've now resolved the incident. Thanks for your patience.
Major November 20, 2025 Expected delivery delays in Belgium in week 48 - due to national strike 17d 18h Postal Services
Started Nov 20, 2025, 03:00 PM UTC· resolved Dec 08, 2025, 09:24 AM UTC
- identified Nov 20, 2025, 03:00 PM UTC
Three days of national strike and demonstrations in the public sector have been announced in Belgium for November 24, 25 and 26. As a result, letter delivery to Belgium is expected to be disrupted on Tuesday the 25th and Wednesday the 26th and likely being delayed through the rest of the week.
- resolved Dec 08, 2025, 09:24 AM UTC
Delivery durations in Belgium have resumed to normal again
Major March 23, 2025 Payments in CHF not automatically processed 1d 4h Payments & Billing
Started Mar 23, 2025, 11:15 AM UTC· resolved Mar 24, 2025, 04:12 PM UTC
- identified Mar 23, 2025, 11:15 AM UTC
We have received several support inquiries regarding CHF-Payments which have not been received / processed. Initial investigations have shown that our bank payment processor is not forwarding us the payment information and there is a delay in processing. This only affects Bank transfers in CHF. We are in contact with our bank payment processor to identify the root cause.
- resolved Mar 24, 2025, 04:12 PM UTC
Our bank payment processor has confirmed the misconfiguration in the delivery of payment information and we have now received all missing information. All payments which were made, but did not result in credit in the pingen account, have been identified and credited a few minutes ago. We have created an incident in our bank to understand why this happened and how it can be prevented in future.