The issue is fully resolved. All API endpoints are responding normally. The expired TLS certificate has been renewed with automatic renewal configured to prevent recurrence. We've also increased monitoring on the proxy service. We apologize for the disruption.

The root cause was an expired TLS certificate on an internal proxy service. This caused upstream requests to time out, which cascaded into widespread 502 errors across the API. After the initial 502s cleared, quote endpoints continued to fail due to the underlying proxy being unreachable. The certificate has been renewed with automatic renewal in place to prevent recurrence. All endpoints are responding normally. We're monitoring to confirm stability.

We have identified a spike in request volume, which contributed to the elevated error rates previously reported. Additionally, we identified that our service responsible for fetching Binance quotes is experiencing abnormally high response times, further impacting quote-related endpoints. We are actively monitoring the situation and working to stabilize response times. Further updates will follow.

502 errors have been resolved and the majority of endpoints are responding normally. We are still seeing 504 timeouts on quote-related requests. We're continuing to work on that and will update again when there is a change.

Almost all API endpoints are currently returning 502 or 504 errors and the service is effectively down. We're working to restore normal operation and will post updates here as the situation changes.

Dashboard authentication is currently unavailable due to an ongoing incident with our auth provider (Clerk). You can follow the status updates here: https://status.clerk.com/

We're monitoring the situation and will keep you posted once it's resolved.

Due to increase of transactions on Polygon and Base, some of them are not fully completed or are delaying. We're investigating all transactions and please reach out to us if you notice something wrong.

Some transactions are getting refunded automatically because of some instabilities in the central bank system. We will keep following closely but none of our services were affected.

We fixed the problem and we will monitor for the whole day.

We're experiencing temporary processing delays across all transactions due to our recent infrastructure migration to a new cloud provider. Our team is actively working to resolve this issue as quickly as possible. All payments currently showing a "processing" status will be completed shortly. We appreciate your patience and will keep you updated on our progress.

Hi everyone, we're experiencing some delays on transactions due to problems in our queue software: https://status.inngest.com/

Some transactions are failing due to issues with our durable functions provider: https://status.inngest.com/

https://www.cloudflarestatus.com/

Some transactions are in processing status forever due to a problem with our queue provider: https://status.inngest.com/

It seems the problem is already solved and we will keep monitoring.

Our FX rate provider is experiencing inconsistent performance across multiple countries. We're currently investigating whether this is due to rate limiting or other technical constraints.

Fixed!

Hi team, we're seeing errors when sending ARS and MXN transactions with our banking partner. We're investigating and will bring updates soon.

Some of transactions are being affected due to AWS outage today: https://health.aws.amazon.com/health/status

We are currently experiencing service disruptions due to network-wide issues affecting the Polygon mainnet. Our RPC provider, QuickNode, has confirmed they are unable to process transactions at this time.

All Polygon mainnet transactions are temporarily unavailable

• Issue affects the entire Polygon network, not isolated to our services
• No estimated time for resolution available

Actions Being Taken:

• Actively monitoring the situation with QuickNode
• Tracking updates via their status page: https://status.quicknode.com/incidents/cjqf5klxfbdh

Next Steps:

• We will provide updates as soon as more information becomes available from our provider or the Polygon network team. Users are advised to avoid attempting Polygon transactions until service is restored.

Solved on June 13.

We are currently experiencing degraded performance affecting payment processing times. While our core systems remain operational, some payouts and payins may experience extended processing delays.

The Brazil payment processing outage incident has been fully resolved as of Monday, March 17, 2025, 9:45am PST.

Root Cause: Our principal banking partner in Brazil froze our API connection for compliance reasons, which resulted in the complete service outage for Brazil transactions.

Resolution: We engaged directly with our banking partner's entire legal and compliance team to resolve the issues as quickly as possible. We regained access to the API this Saturday and completed testing to ensure stable operations. Additionally, we have successfully integrated with a secondary banking partner for Brazil operations.

Duration: Thursday, March 13, 2025, 2:30pm PST to Monday, March 17, 2025, 9:45am PST

Preventative Measures:

• All payins and payouts from Brazil are now fully normalized and operational
• We have added one more banking partner for redundancy to ensure business continuity in case of similar issues
• Implementing enhanced monitoring for early detection of API authentication issues
• Establishing improved communication channels with banking partners for faster resolution of technical issues

We sincerely apologize for any disruption this incident may have caused and appreciate your patience during the resolution process. We understand the impact this had on your business operations and have taken significant steps to prevent similar incidents in the future.

If you experience any issues with Brazil payment processing, please contact our support team immediately.