Is there an Tangany outage?
Tangany status: Systems Active
Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Tangany and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Tangany and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Tangany.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| API Gateway | Active |
| Tangany Partner Portal | Active |
| Tangany Custody API | Active |
| API backend | Active |
| Bitcoin Mainnet | Active |
| Bitcoin Testnet | Active |
| BNB Chain Mainnet | Active |
| BNB Chain Testnet | Active |
| Ethereum Goerli | Active |
| Ethereum Mainnet | Active |
| Ethereum Sepolia | Active |
| Gnosis Chiado | Active |
| Gnosis Mainnet | Active |
| Polygon Mainnet | Active |
| Polygon Mumbai | Active |
| Tezos Mainnet | Active |
| Tangany Customers API | Active |
| API backend | Active |
| Tangany Settlement API | Active |
| API backend | Active |
| Web Resources | Active |
| docs.tangany.com | Active |
| support.tangany.com | Active |
| tangany.com | Active |
View the latest incidents for Tangany and check for official updates:
Description: We are pleased to inform you that the issue affecting our 'docs.tangany.com' has been resolved, and the webpage is now fully available. We apologize for any inconvenience this may have caused and appreciate your patience. Here are the impact duration details, The impact started at:12:30 CEST The impact ended at: 16:30 CEST If you experience any further issues, please don't hesitate to contact us. Thank you for your understanding. Best regards, Tangany Support Team
Status: Resolved
Impact: Major | Started At: Oct. 1, 2024, 11:58 a.m.
Description: We experienced a brief disruption in connectivity to the Settlement API during the recent maintenance window. We are happy to report that the issue has been fully resolved, and all services are now functioning normally. We apologize for any inconvenience this may have caused and thank you for your understanding. Here is the impact duration. For any further questions or assistance, please contact us at [email protected]. Impact Started: 9/25/2024, 15:14:36 CEST Impact Resolved: 9/25/2024, 17:04:00 CEST
Status: Resolved
Impact: Minor | Started At: Sept. 25, 2024, 1 p.m.
Description: Our CSP resolved the impact at 22:48 CEST. Incident details published by Microsoft are mentioned below for reference. What happened? Between approximately at 11:45 UTC and 19:43 UTC on 30 July 2024, a subset of customers may have experienced issues connecting to a subset of Microsoft services globally. Impacted services included Azure App Services, Application Insights, Azure IoT Central, Azure Log Search Alerts, Azure Policy, as well as the Azure portal itself and a subset of Microsoft 365 and Microsoft Purview services. What do we know so far? An unexpected usage spike resulted in Azure Front Door (AFD) and Azure Content Delivery Network (CDN) components performing below acceptable thresholds, leading to intermittent errors, timeout, and latency spikes. While the initial trigger event was a Distributed Denial-of-Service (DDoS) attack, which activated our DDoS protection mechanisms, initial investigations suggest that an error in the implementation of our defenses amplified the impact of the attack rather than mitigating it. How did we respond? Customer impact began at 11:45 UTC and we started investigating. Once the nature of the usage spike was understood, we implemented networking configuration changes to support our DDoS protection efforts, and performed failovers to alternate networking paths to provide relief. Our initial network configuration changes successfully mitigated majority of the impact by 14:10 UTC. Some customers reported less than 100% availability, which we began mitigating at around 18:00 UTC. We proceeded with an updated mitigation approach, first rolling this out across regions in Asia Pacific and Europe. After validating that this revised approach successfully eliminated the side effect impacts of the initial mitigation, we rolled it out to regions in the Americas. Failure rates returned to pre-incident levels by 19:43 UTC - after monitoring traffic and services to ensure that the issue was fully mitigated, we declared the incident mitigated at 20:48 UTC. Some downstream services took longer to recover, depending on how they were configured to use AFD and/or CDN. What happens next? Our team will be completing an internal retrospective to understand the incident in more detail. We will publish a Preliminary Post Incident Review (PIR) within approximately 72 hours, to share more details on what happened and how we responded. After our internal retrospective is completed, generally within 14 days, we will publish a Final Post Incident Review with any additional details and learnings. To get notified when that happens, and/or to stay informed about future Azure service issues, make sure that you configure and maintain Azure Service Health alerts – these can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/ash-alerts. For more information on Post Incident Reviews, refer to https://aka.ms/AzurePIRs. Finally, for broader guidance on preparing for cloud incidents, refer to https://aka.ms/incidentreadiness.
Status: Resolved
Impact: Minor | Started At: July 30, 2024, 2:51 p.m.
Description: We had a partial outage on our service(Settlement and Custody API). During this time window, some settlement accounts and Custody wallet creation requests failed due to the internal link disconnection with Customer data from these services. The impact has been restored, and the following are the impact/restoration time details for reference. Impact start time: 18:00, 12 June 2024 Wednesday. Service Restoration time: 09:00, 13 June 2024 Thursday. Impacted Services: Settlement API(account creation call), Custody API(Wallet creation call)
Status: Resolved
Impact: Minor | Started At: June 12, 2024, 4 p.m.
Description: We had a partial outage on our service(Settlement and Custody API). During this time window, some settlement accounts and Custody wallet creation requests failed due to the internal link disconnection with Customer data from these services. The impact has been restored, and the following are the impact/restoration time details for reference. Impact start time: 18:00, 12 June 2024 Wednesday. Service Restoration time: 09:00, 13 June 2024 Thursday. Impacted Services: Settlement API(account creation call), Custody API(Wallet creation call)
Status: Resolved
Impact: Minor | Started At: June 12, 2024, 4 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
