Subscribe to UpdatesSubscribe
Get email notifications whenever Silverflow creates, updates or resolves an incident.
Get text message notifications whenever Silverflow creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get incident updates and maintenance status messages in Microsoft Teams channel.
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Visit our support site.
All Systems Operational
About This Site
This status page tracks performance across a variety of products and services available on the Silverflow platform. It does not represent the service level commitments in your agreement with Silverflow.
Past Incidents
Jul 16, 2026
No incidents reported today.
Jul 15, 2026
Resolved -
As of 13:03 CET the issue of not being able to complete the Mastercard 3D Secure Challenge flow has been resolved. All Mastercard 3D Secure services are now operating as expected. We will continue monitoring our systems to ensure ongoing stability.
Jul 15, 13:19 CEST
Jul 15, 13:19 CEST
Identified -
Mastercard has Acknowledged that the issue is on their side. We are waiting for them to resolve the issue and will keep monitoring.
Jul 15, 11:57 CEST
Jul 15, 11:57 CEST
Investigating -
As of 10:54 CET we have identified an issue with completing the Mastercard 3D Secure challenge flow. We have reached out to Mastercard and will continue monitoring.
Jul 15, 11:41 CEST
Jul 15, 11:41 CEST
Resolved -
As of 10:10 CET, we have seen full recovery in Mastercard 3D Secure Authentications.
Jul 15, 11:10 CEST
Jul 15, 11:10 CEST
Monitoring -
Mastercard has acknowledged an ongoing issue on their end, affecting 3D Secure authentications starting from 08:59 CET. We will keep monitoring until Mastercard has resolved the issue on their end.
Jul 15, 09:53 CEST
Jul 15, 09:53 CEST
Identified -
At around 09:00 CET we noticed an increase in Mastercard 3DS 5xx errors. At this moment this is still ongoing and no Mastercard 3DS request are successful. We have reached out to Mastercard and will continue monitoring.
Jul 15, 09:44 CEST
Jul 15, 09:44 CEST
Investigating -
We are currently observing a high rate of failing 3DS requests for Mastercard.
Jul 15, 09:29 CEST
Jul 15, 09:29 CEST
Jul 14, 2026
No incidents reported.
Jul 13, 2026
No incidents reported.
Jul 12, 2026
Resolved -
Between 16:37 and 16:55 CEST, we experienced an issue where 51.30% of all Mastercard 3DS requests failed across multiple issuers. Our investigation confirmed this was caused by an influx of improperly formatted error messages received directly from Mastercard.
The issue subsided at 16:55 CEST, and our monitoring confirms that 3DS authentication for Mastercard has remained fully stable since then.
Jul 12, 17:41 CEST
The issue subsided at 16:55 CEST, and our monitoring confirms that 3DS authentication for Mastercard has remained fully stable since then.
Jul 12, 17:41 CEST
Monitoring -
Our engineering team has identified that the elevated 3DS error rates were caused by an influx of invalid error messages originating from Mastercard.
These errors subsided at approximately 16:56 CEST. We are now actively monitoring the situation to ensure full stability is maintained.
Jul 12, 17:11 CEST
These errors subsided at approximately 16:56 CEST. We are now actively monitoring the situation to ensure full stability is maintained.
Jul 12, 17:11 CEST
Investigating -
We are currently observing a high rate of failing 3DS requests. Our engineering team is actively investigating
Jul 12, 16:52 CEST
Jul 12, 16:52 CEST
Jul 11, 2026
No incidents reported.
Jul 10, 2026
No incidents reported.
Jul 9, 2026
No incidents reported.
Jul 8, 2026
No incidents reported.
Jul 7, 2026
No incidents reported.
Jul 6, 2026
Resolved -
Timeframe: July 6, 2026, between 14:55 and 14:58 CEST
During the brief window noted above, the following endpoints returned a number of HTTP 500 errors:
POST /v1/charges/:chargeKey/clear
POST /v1/charges/:chargeKey/reverse
GET /v1/charges/:chargeKey/actions
GET /v1/charges/:chargeKey/actions/:actionKey
Root Cause & Impact
This was due to a faulty deployment. Only a minimal number of requests were impacted during this three-minute window.
Next Steps & Required Actions
The issue has been fully resolved on our end. The main action needed from affected acquirers is to resubmit any failed clearing actions.
Jul 6, 15:45 CEST
During the brief window noted above, the following endpoints returned a number of HTTP 500 errors:
POST /v1/charges/:chargeKey/clear
POST /v1/charges/:chargeKey/reverse
GET /v1/charges/:chargeKey/actions
GET /v1/charges/:chargeKey/actions/:actionKey
Root Cause & Impact
This was due to a faulty deployment. Only a minimal number of requests were impacted during this three-minute window.
Next Steps & Required Actions
The issue has been fully resolved on our end. The main action needed from affected acquirers is to resubmit any failed clearing actions.
Jul 6, 15:45 CEST
Jul 5, 2026
No incidents reported.
Jul 4, 2026
No incidents reported.
Jul 3, 2026
No incidents reported.
Jul 2, 2026
No incidents reported.