WSO2 is now Choreo LabsLearn more

Trusted AI Governance
Build

Create agents and AI apps with the tools and languages your teams already use.

Connect

Link agents securely to your APIs, data, models and business systems.

Run

Deploy, observe and operate agents and AI apps reliably at any scale.

Govern

Control identity, access, cost and policy for every agent in production.

Agent Management

Developer Platform

  • API Management Cloud

    Design, secure and publish APIs with governance and analytics built in.

    Sign Up Now
  • Integration Cloud

    Connect apps, data and AI agents with low-code and pro-code integration.

    Sign Up Now
  • Identity & Access Management Cloud

    Secure sign-in and access for customers, partners, workforce and agents.

    Sign Up Now
  • Agent Management Cloud

    Build, run and govern AI agents with full visibility and control.

    Sign Up Now
  • Developer Platform Cloud

    Ship cloud-native apps faster on an internal developer platform.

    Sign Up Now

Self-Hosted

Full control over your stack. Deploy directly to your own servers, bare metal, cloud, or Kubernetes environment. Your data never leaves your perimeter.

Product Downloads
Choreo Labs
AI Governance
Platform
Solutions
Resources
Blog

WSO2 cloud incident report: jan 21, 2016

WSO2 Cloud faced a serious degradation of service due to DNS failing to resolve addresses related to WSO2 Cloud URLs on 21st January 2016. Here is the incident report and actions taken.

Start time: January 21, 2016 0923 PST
Recovery time: January 21, 2016, 1001 PST

Impact:

  • Reachability to all WSO2 Cloud functionalities was disrupted.
  • Partial service downtime due to DNS resolve failures for some parts of the world.
  • There was a 38-minute gateway downtime during this incident : https://uptime.cloud.wso2.com/

Root cause:
Verification failure between WSO2 name-service provider and ICANN has resulted in disabling of WSO2 domains. Since WSO2 Cloud is run under a subdomain of wso2.com WSO2 Cloud was also impacted with the domain disabling. It is observed that this has not affected to some regions because caching servers were still resolving for those regions.

Actions:

  • As soon as our monitoring tools alerted us regarding the outage we escalated it to our infrastructure team.
  • They managed to resolve the situation by contacting the relevant parties and getting the services up.
  • Infrastructure team updated the contact details for the internet domain to ensure that verification calls always reach the team.