Saxo reports Operational
No reported issues with this provider’s services in the last 24 hours.
Saxo status history
- Down
- Warning
- Jul 17
- Jul 24
- Jul 31
- Aug 7
- Aug 14
- Aug 16
- Aug 21
- Aug 23
- Aug 28
- Aug 30
- Sep 4
- Sep 6
- Sep 11
- Sep 13
- Sep 15
- Sep 18
- Sep 20
- Sep 22
- Sep 25
- Sep 27
- Sep 29
- Oct 2
- Oct 4
- Oct 6
- Oct 9
- Oct 11
- Oct 13
Incidents
Provider incidents
No incidents from provider for the last 30 days.
We'll keep monitoring and show any new events here.
Community reports
No community reports yet
No users have reported issues with this provider yet.
About Saxo status page
- Monitoring since Oct 2026
Saw an error in description or reports for Saxo?
Frequently asked questions
Quick answers for payment teams and merchants investigating an incident. Firemap explains the evidence; it does not diagnose your merchant account.
No. Saxo currently reports normal operation on its official status page.
They are the states Saxo publishes on its official status page. Operational means the service works normally. Degraded means part of it is slower or failing for some customers, regions or payment methods, while the rest still works. Outage means a major disruption: a service, or a key part of it, is unavailable. Resolved marks an incident Saxo has closed; the time it was resolved shows when you hover it.
Not on its own. Firemap shows what Saxo publishes about its platform, not the state of your account. An incident may affect only some regions, payment methods or integrations. Check your own transaction logs and decline codes, and contact Saxo support with specific transaction IDs if you see failures.
From official status pages only. Firemap reads each page it tracks automatically every few minutes and records every status change and incident the provider publishes there. Nothing about Saxo is added or edited by hand.
They come from different sources. The official status is what Saxo has confirmed, and providers often post an incident only after the first failures. Community reports come from users and can show a problem earlier, but it may be local: one bank, one country or one integration. Treat reports without an official incident as an early signal, not a confirmed outage.
Start with your own data: error rates, decline codes and response times by payment method, card scheme and country. Compare them with the scope of the incident on the status page. Make sure the backup provider supports the same methods and currencies, move a small share of traffic first, and switch back once the incident is resolved and your metrics recover.
Firemap tracks the official status pages of payment providers listed on PayAtlas. Each page is checked automatically, and every incident is stored with its start time and, once resolved, its end time. When Firemap has data for Saxo, this page shows up to 90 days of status history and incidents from the last 30 days.
Firemap can confirm only what Saxo has published on its status page: the current status, incidents with their start time and, once resolved, end time, and how long the page has been tracked. It cannot confirm the impact on a specific merchant, transaction or region unless Saxo says so, and it cannot see problems the provider has not reported.
PayAtlas Stack
Manage Your Payment Stack in One Place
Save the providers you work with and get instant access to their status, coverage, insights, comparisons, and recommended alternatives whenever you need them.
- Free monitoring
- 5 minutes setup