Form3 Staging Outage History
Form3 Staging is up right nowPingoru has recorded 49 incidents for Form3 Staging: 3 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 1 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 1 | 4 of 720 (1%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 518 (0%) |
Incidents, newest first
Minor June 18, 2026 INC465496 - Degradation Form3 - UK Instant Simulator 3h 41m Direct (LON), Direct (MQ), Direct (WS)
Started Jun 18, 2026, 08:17 AM UTC· resolved Jun 18, 2026, 11:58 AM UTC
- investigating Jun 18, 2026, 08:17 AM UTC
We have identified an issue impacting the FPS Direct simulator. Our engineers are currently investigating and further details will be posted as the investigation progresses
- investigating Jun 18, 2026, 08:27 AM UTC
We are continuing to investigate the issues on the FPS simulator. Payments processing may have failures or increased processing times.
- identified Jun 18, 2026, 09:54 AM UTC
We have applied a temporary fix. The FPS Simulator has returned to normal processing times. We will provide a further update as more information becomes available.
- monitoring Jun 18, 2026, 11:54 AM UTC
A full fix has been implemented and and are now in a period of monitoring. Customers using the Simulator should now see that normal processing has resumed.
- resolved Jun 18, 2026, 11:58 AM UTC
The issue affecting FPS Simulator has been resolved. We have confirmed, following a period of monitoring, that the service has returned to normal processing and no further degradation has been observed. Further details will be provided in the postmortem in due course.
- postmortem Jun 19, 2026, 08:55 AM UTC
Form3 identified an issue within the FPS Simulator in the Staging environment that impacted customer testing activities. During the incident period, payment transactions either failed to process or experienced significant delays. A fix was implemented, and full service was restored at 12:53 BST on 18th June. Form3 continues to proactively monitor the Staging environment and is reviewing opportunities for further improvements to help prevent similar issues from affecting customer testing in the future.
Major April 20, 2026 Staging Platform Issue 38m FPS RT - Direct, Direct, FedNow, VoP Responder and 16 more
Started Apr 20, 2026, 08:49 AM UTC· resolved Apr 20, 2026, 09:27 AM UTC
- investigating Apr 20, 2026, 08:49 AM UTC
We have identified an issue impacting all Staging environment services. Our engineers are currently investigating and we will provide further details as the investigation continues
- resolved Apr 20, 2026, 09:27 AM UTC
Our Staging Platform Incident has recovered and normal service has resumed. We will continue to monitor the service to ensure there is no ongoing impact.
- postmortem Apr 21, 2026, 09:37 AM UTC
Form3 identified an issue within the Staging environment impacting both admission and submission flows. A fix was implemented, and service was fully restored at 09:17 UTC on 20 April 2026. Form3 continues to proactively monitor the Staging environment to identify improvements and prevent impact to customer testing.
Minor March 30, 2026 INC443812 - Notifications not being sent 2h Direct, VoP Responder, Direct Non Settling, Direct (LON) and 7 more
Started Mar 30, 2026, 01:30 PM UTC· resolved Mar 30, 2026, 03:30 PM UTC
- resolved Mar 30, 2026, 04:07 PM UTC
Form3 identified an issue impacting notifications on the Staging environment between 13:30 - 15:30 UTC. During this period, no notifications were being sent. After a period of monitoring, our Incident Response Team have confirmed notifications are working as expected.
- postmortem Mar 31, 2026, 08:50 AM UTC
Form3 were alerted to an issue affecting the notification service in the staging environment, where notifications were not being delivered as expected between 13:30 - 15:30 UTC on 30/03/26. A fix was implemented and service has been confirmed as restored. Form3 continue to proactively monitor the staging environment to ensure stability and support customer testing.
Notice July 8, 2025 INC390509 - Degradation to the Form3 - Confirmation of Payee Service 1h 2m CoP Responder (LON), CoP Requester (LON)
Started Jul 08, 2025, 01:27 PM UTC· resolved Jul 08, 2025, 02:30 PM UTC
- resolved Jul 08, 2025, 01:27 PM UTC
An issue impacting the Form3 - Confirmation of Payee Service was identified. An error would have been seen for CoP Requests made between 13:38 UTC on 07/07/2025 > 14:30 UTC 08/07/2025 A fix has been successfully implemented and service is restored.
- postmortem Jul 08, 2025, 01:32 PM UTC
Form3 were alerted to an issue on our Form3 - Confirmation of Payee simulator between 13:38 UTC on 07/07/2025 > 14:30 UTC 08/07/2025 A fix was implemented and service was confirmed as restored at 14:30 UTC 08/07/2025 Form3 continue to proactively monitor the Staging environment to identify service enhancement and prevent impact to customer testing.
Critical April 30, 2025 INC376826 - Outage to the Form3 - US Instant Simulator 15m FedNow, TCH - RTP
Started Apr 30, 2025, 10:09 AM UTC· resolved Apr 30, 2025, 10:24 AM UTC
- investigating Apr 30, 2025, 10:09 AM UTC
We have identified an issue impacting the Form3 - US Instant Simulator. Our engineers are currently investigating and we will provide further details as the investigation continues.
- resolved Apr 30, 2025, 10:24 AM UTC
The issue affecting Form3 - US Instant Simulator has been resolved and normal service has resumed. We will continue to monitor the service to ensure there is no ongoing impact.
Notice March 17, 2025 INC367758 Staging Environment Unavailable in Ramwong – Direct, Direct Non Settling, Direct (IRE), Direct Non Settling (IRE) and 5 more
Started Mar 17, 2025, 02:08 PM UTC· resolved Mar 17, 2025, 02:08 PM UTC
- resolved Mar 17, 2025, 02:08 PM UTC
Form3 identified an issue on the Ramwong Staging Environment. This impacted all payment submissions being created, there was no impact to inbound payments. The issue was fixed at 10:16 UTC.