Ande Outage History

Ande is up right now

Ande had 3 outages in the last 2 years totaling 6h 24m of downtime, averaging 0.1 incidents per month.

There were 3 Ande outages since July 23, 2025 totaling 6h 24m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.ande.ai

Major October 20, 2025

AWS Major Outage

Detected by Pingoru
Oct 20, 2025, 03:52 PM UTC
Resolved
Oct 20, 2025, 09:21 PM UTC
Duration
5h 28m
Affected: WebsiteMobile ApplicationIntegrationsPayment APIsAI Agent
Timeline · 3 updates
  1. monitoring Oct 20, 2025, 03:52 PM UTC

    We're actively monitoring outages in AWS's us-east-1 region. Components of the DineWise platform are non-operational. In the News: https://www.cnn.com/business/live-news/amazon-tech-outage-10-20-25-intl AWS Health Dashboard: https://health.aws.amazon.com/health/status

  2. monitoring Oct 20, 2025, 06:20 PM UTC

    We're seeing some improved reliability from AWS. We are continuing to monitor AWS's progress.

  3. resolved Oct 20, 2025, 09:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 21, 2025

Authentication Service Outage

Detected by Pingoru
Aug 21, 2025, 06:14 PM UTC
Resolved
Aug 21, 2025, 07:10 PM UTC
Duration
56m
Affected: WebsiteMobile ApplicationAI Agent
Timeline · 3 updates
  1. investigating Aug 21, 2025, 06:14 PM UTC

    Our authentication system (WorkOS) is experiencing partial outages that are affecting our system. We are actively monitoring their status at https://status.workos.com

  2. identified Aug 21, 2025, 06:24 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Aug 21, 2025, 07:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 23, 2025

This is an example incident

Detected by Pingoru
Jul 23, 2025, 02:33 PM UTC
Resolved
Jul 23, 2025, 02:33 PM UTC
Duration
–
Timeline · 4 updates
  1. investigating Jul 24, 2025, 02:17 PM UTC

    When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

  2. identified Jul 24, 2025, 02:17 PM UTC

    As you continue to work through the incident, update your customers frequently.

  3. monitoring Jul 24, 2025, 02:17 PM UTC

    Let your users know once a fix is in place, and keep communication clear and precise.

  4. resolved Jul 24, 2025, 02:17 PM UTC

    Empathize with those affected and let them know everything is operating as normal.

Read the full incident report →