Conferma Status

Sep 3, 2026

No incidents reported today.

Sep 2, 2026

Scheduled Maintenance: PAPI API Feature Improvements

Completed - The scheduled maintenance has been completed.
Sep 2, 07:00 BST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 2, 06:00 BST

Scheduled - We will be implementing feature improvements to the papi.conferma.com API on Wednesday, 02 September at 06:00 GMT.
No service impact is expected as a result of this change. However, if you have any questions or concerns, please contact a member of the Conferma team for further information.
Aug 28, 13:19 BST

Sep 1, 2026

No incidents reported.

Aug 31, 2026

No incidents reported.

Aug 30, 2026

No incidents reported.

Aug 29, 2026

Transaction File Import Delays

Resolved - We are pleased to confirm that previously delayed imported transaction data files have now been successfully processed.

All associated data is now available as expected.

We apologise for any inconvenience caused and thank you for your patience while we worked to resolve the issue.
Aug 29, 10:51 BST

Investigating - We are currently experiencing a delay in the processing of transaction data due to transaction files not yet being received.

Our teams are actively investigating and working to restore normal processing.

We apologise for any inconvenience this may cause and will provide a further update once the files have been received and processing has completed.
Aug 29, 07:26 BST

Aug 28, 2026

No incidents reported.

Aug 27, 2026

No incidents reported.

Aug 26, 2026

Scheduled Maintenance: PAPI API Feature Improvements

Completed - The scheduled maintenance has been completed.
Aug 26, 07:00 BST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 26, 06:00 BST

Scheduled - We will be implementing feature improvements to the papi.conferma.com API on Wednesday, 26 August at 06:00 GMT.
No service impact is expected as a result of this change. However, if you have any questions or concerns, please contact a member of the Conferma team for further information.
Aug 20, 14:26 BST

Aug 25, 2026

No incidents reported.

Aug 24, 2026

Data Handoff Reporting Delays

Resolved - This incident has been resolved.
Aug 24, 08:11 BST

Monitoring - Reporting data has now been successfully re-queued and processing has resumed.

We are currently working through the backlog of reports generated during the disruption. We expect this backlog to clear over the coming hours, with normal reporting service anticipated to be fully restored by the morning.

Our teams will continue to closely monitor the service throughout the weekend to ensure processing continues as expected.

We apologise for any inconvenience caused and thank you for your patience.
Aug 21, 20:47 BST

Investigating - We are currently experiencing a delay in the handoff and processing of reporting data.

The affected reports are expected to be re-queued by 22:00 UTC. Our teams are actively working to restore normal processing and minimise any impact.

We will provide a further update as progress is made.

We apologise for any inconvenience caused.
Aug 21, 15:43 BST

Aug 23, 2026

No incidents reported.

Aug 22, 2026

No incidents reported.

Aug 21, 2026

Aug 20, 2026

Delays in One-Time Passcode Delivery

Resolved - Changes have been deployed to optimise OTP processing and increase service throughput. As a result, the backlog is now being processed successfully and delivery times are returning to expected levels.

As the queue continues to clear, some users may receive delayed OTP messages that were originally generated yesterday. We are continuing to monitor the service closely and recovery remains on track.

We apologise for any inconvenience caused and thank customers for their patience.
Aug 20, 11:15 BST

Investigating - We are currently investigating delays affecting the delivery of one-time passcodes (OTPs) for a subset of customers.

Customers may experience longer than expected wait times when requesting OTPs. In some cases, an OTP may arrive after a newer OTP has already been requested, causing the original code to be invalid on receipt.

Our teams are actively working to identify the cause and restore normal service as quickly as possible. We apologise for any inconvenience this may cause and will provide further updates as more information becomes available.
Aug 20, 10:08 BST

All Systems Operational

Past Incidents