Is Connexpay down?
Connexpay is operational.
There are no reported issues with this provider’s services in the last 24 hours.
Updated just now
Reliability snapshot
Last 30 days
Incidents timeline
1 peak
1 peak
1 peak
- Operational
- Degraded
- Partial outage
- Major outage
- Community report
-
Aug 20
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 1
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 1
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Sep 11
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 1
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Sep 19
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 1
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 1
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Oct 4
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Oct 19
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 1
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 1
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Oct 26
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 1
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 1
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Nov 2
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Nov 3
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 1
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Nov 10
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Nov 17
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
Community reports
No community reports yet
No community members have reported issues with this provider.
Is Connexpay down for you?
-
∙ Duration 12h
We are aware that certain users are currently not receiving emails containing their multi-factor authentication code. All ConnexPay services are fully operational and running as expected.
If you are experiencing issues receiving email notifications or one-time authentication codes, please be aware that this is linked to an ongoing service disruption with Microsoft affecting email delivery and is unrelated to ConnexPay's platform.
You can track the latest updates directly on Microsoft's official status page: https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect
**Recommended Action:** If you use email-based MFA to access Bridge, we recommend using the text message authentication option as a more reliable alternative while this issue persists.
This incident has been resolved.Resolved 3d ago
Resolved
-
Partial outage∙ Duration 1h
Affected: US-Daily Accounting File (DAF) CA-Daily Accounting File (DAF) EU-Daily Accounting File (DAF)
Our teams have identified an issue that is causing our Settlement reports to be delayed. We are actively working to publish the reports as quickly as possible. We will provide updates as soon as they are available.
The issue causing DAF delivery delays has been resolved. A fix was implemented and delivery has returned to normal across all regions. If you continue to experience delays, please contact support.Partial outage → Resolved 2w ago
Resolved
-
Partial outage∙ Duration 5h
Affected: Bridge UI
Our team has been made aware of a Microsoft Azure service outage that is affecting MFA emails for Connexpay Bridge. This outage is affecting verification emails that are typically sent when logging into Bridge UI. During this outage, you will not be able to log into Bridge UI using MFA email verification. SMS MFA verification is not affected. Other services and our APIs are not affected. We will provide updates as more information becomes available.
We are continuing to monitor this issue and will continue to update as more information is available from the vendor.
We are continuing to monitor this issue and will continue to update as more information is available from the vendor.
We are continuing to monitor this issue and will continue to update as more information is available from the vendor.
Microsoft has identified the cause of the issue, and a fix is currently in progress. We are continuing to monitor this issue and will continue to update as more information is available from the vendor.
Microsoft has identified the cause of the issue, and a fix is currently in progress. We are continuing to monitor this issue and will continue to update as more information is available from the vendor.
Microsoft is still deploying a fix for this issue. Delayed MFA emails may be received while recovery is in process, and some users may receive working MFA codes upon request. In the meantime, we will continue to monitor until full recovery is achieved. We ask that any customers that are able to log in take this opportunity to set up SMS Verification as a secondary method, which was not affected by this issue.
A fix has been implemented by Microsoft, and we are monitoring the results. We ask that any customers that are able to log in take this opportunity to set up SMS Verification as a secondary method, which was not affected by this issue.
A fix implemented by our cloud provider has been successfully applied, and users are now able to request MFA codes through Bridge without issue. We are continuing to monitor the system closely for any potential anomalies, but users should now be able to log in successfully. We ask that any customers that are able to log in take this opportunity to set up SMS Verification as a secondary method, which was not affected by this issue.Partial outage → Resolved 3w ago
Resolved
-
Partial outage∙ Duration 42m
Affected: US-Daily Accounting File (DAF) CA-Daily Accounting File (DAF) EU-Daily Accounting File (DAF)
Our teams have identified an issue that is causing our Settlement reports to be delayed. We are actively working to publish the reports as quickly as possible. We will provide updates as soon as they are available.
The issue causing DAF delivery delays has been resolved. A fix was implemented and delivery has returned to normal across all regions. If you continue to experience delays, please contact support.Partial outage → Resolved 3w ago
Resolved
Services
No currently affected Connexpay services
There are no reported issues with this provider’s services in the last 24 hours.
-
Card Issuance
Operational -
Transaction Processing
Operational -
Purchases API
Operational -
Webhooks
Operational -
ACH Purchases
Operational -
Card Issuance
Operational -
Transaction Processing
Operational -
Purchases API
Operational -
Webhooks
Operational -
Credit Sales (Apple, Google, Etc.)
Operational -
3DS Sales and Authentication
Operational -
Sales API
Operational -
ACH Sales
Operational -
SDK
Operational -
Hosted Payments Page
Operational -
Webhooks
Operational -
Credit Sales
Operational -
3DS Sales and Authentication
Operational -
Sales API
Operational -
SDK
Operational -
Hosted Payments Page
Operational -
Webhooks
Operational -
US-Daily Accounting File (DAF)
Operational -
CA-Daily Accounting File (DAF)
Operational -
EU-Daily Accounting File (DAF)
Operational -
Analytics UI
Operational -
Bridge API
Operational -
Bridge UI
Operational -
Payment Valet - UI
Operational -
Payment Valet - File Processing
Operational -
CMS API
Operational -
CMS UI
Operational -
ATA
Operational -
ATI
Operational -
Sandbox
Operational
About Connexpay status page
- Monitoring since Oct 2026
- 35 services and components tracked
- 57 incidents total
- Last updated: Nov 17, 2026
Saw an error in description or reports for Connexpay?
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. Connexpay reports normal operation on its official status page. Firemap last read the status page today at 14:06 UTC.
They are the four status levels Firemap uses for Connexpay, the same scale most status pages use. Operational means everything works normally. Degraded means the services work, but some are slower or return more errors than usual. Partial outage means some services, regions or payment methods are unavailable, while the rest still work. Major outage means a key service is unavailable for most customers. The same levels color the status banner, the official incidents and the services. When Connexpay publishes it, each official incident also shows its stage: Investigating, Identified, Monitoring or Resolved. In the Incidents timeline, each day shows its incidents by level, and a purple strip marks days with community reports.
Uptime is the share of time in the last 30 days when Connexpay reported normal operation on its status page. Degraded performance and outages count as downtime. Time when Firemap could not read the page counts as normal, because there is no evidence of a problem. The value is rounded down to two decimals. When Firemap has data for Connexpay, the Reliability snapshot shows Uptime next to three more numbers: Incidents, the official incidents that started in the last 30 days; Community reports from the same days; and Service availability, the share of Connexpay services that work normally right now. Incidents, Community reports and Uptime are compared with the previous 30 days. If Firemap has not tracked Connexpay for that long, Incidents and Uptime show “No data for previous 30 days”.
Select an incident in the Official incidents block. A panel opens with the incident level, the affected services when the status page lists them, the start and, once resolved, the end time, and the updates Connexpay posted, newest first. Each update shows when it was posted and its stage: Investigating, Identified, Monitoring or Resolved. Some status pages publish updates without stages, or no separate updates at all; the panel then shows the updates without a stage, or says that there are none.
Not on its own. Firemap shows what Connexpay 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 Connexpay support with specific transaction IDs if you see failures.
From the official Connexpay status page, once Firemap has connected it. Firemap then reads the page automatically every few minutes and records each status change, incident and incident update Connexpay publishes there. Community reports come from PayAtlas users and appear in their own block; they do not change the official status.
They come from different sources. Official incidents are what Connexpay has confirmed, and providers often post one 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.
Use Report issue on this page or, when there are no reports yet, one of the problem buttons in the Community reports block. Sign in, choose what you see: Completely down, Partial outage, Very slow or Showing errors, and describe the problem: what fails, where and since when. Your report appears in the Community reports block at once. Reports do not change the official status of Connexpay.
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.
It shows how old the data is instead of guessing. When Firemap has a status for Connexpay, the top of this page shows when Firemap last read the official status page, for example “Updated 2h ago”. If a check fails, the page keeps the last status Firemap read, with its time. If there has been no reading for 7 days, or Firemap has no working status page for Connexpay, the page shows “Status page not connected” instead of a status. The Incidents timeline counts incidents, so a day without incidents stays green even if the page could not be read that day.
Firemap tracks the official status pages of payment providers listed on PayAtlas. It checks each page automatically and stores every incident with its start time and, once resolved, its end time. When Firemap has data for Connexpay, this page shows an Incidents timeline of up to 90 days, every official incident that is still open and the resolved incidents that started in the last 30 days. Community reports from the last 30 days are shown for every provider.
Firemap can confirm only what Connexpay has published on its status page: the current status, incidents with their start time and, once resolved, end time, the services and updates the status page lists for each incident, and how long the page has been tracked. It cannot confirm the impact on a specific merchant, transaction or region unless Connexpay says so, and it cannot see problems the provider has not reported.
PayAtlas Firemap
Monitor the health of 200+ payment providers, track active incidents, and spot ecosystem-wide disruptions in real time.
Stay on top of your payment stack
Add your payment providers to Stack and get updates on incidents, outages and service status changes in one place.
- Monitor the providers you rely on
- Get notified about status changes
- Spot issues before they affect your payments
Incident Updates Timeline
Couldn’t load the incident.