Monkey Exchange Outage History

Monkey Exchange is up right now

Monkey Exchange had 5 outages in the last 2 years totaling 17h 42m of downtime, averaging 0.2 incidents per month.

There were 5 Monkey Exchange outages since June 16, 2025 totaling 17h 42m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.monkey.exchange

Minor October 10, 2026

We are currently experiencing a performance degradation issue affecting platform.

Detected by Pingoru
Oct 10, 2026, 11:10 AM UTC
Resolved
Oct 10, 2026, 11:43 AM UTC
Duration
33m
Affected: PORTALPORTALPORTALPORTALAPIAPIAPIAPI
Timeline · 5 updates
  1. investigating Oct 10, 2026, 11:10 AM UTC

    We are currently experiencing performance degradation affecting the Supply Plus platform in Brazil, Chile, Mexico, and the United States.

  2. identified Oct 10, 2026, 11:14 AM UTC

    Our team has identified an issue with a caching infrastructure issue and is actively working to restore normal service.

  3. monitoring Oct 10, 2026, 11:18 AM UTC

    The issue has been resolved, and we are currently monitoring the platform to ensure service stability.

  4. monitoring Oct 10, 2026, 11:30 AM UTC

    The issue has been resolved, and we continue to closely monitor the platform to ensure service stability.

  5. resolved Oct 10, 2026, 11:43 AM UTC

    The incident affecting the Supply Plus platform in Brazil, Chile, Mexico, and the United States has been fully resolved. All services are operating normally, and platform performance has been restored. We apologize for any inconvenience caused.

Read the full incident report →

Minor February 16, 2026

[BRASIL] [CHILE] - We are currently experiencing a performance degradation issue affecting platform.

Detected by Pingoru
Feb 16, 2026, 12:09 AM UTC
Resolved
Feb 16, 2026, 05:18 AM UTC
Duration
5h 8m
Affected: PORTALREPORTNOTIFICATIONWEBHOOKSINTEGRATIONAPIOPERATIONS
Timeline · 4 updates
  1. investigating Feb 16, 2026, 12:09 AM UTC

    We are currently investigating this issue.

  2. identified Feb 16, 2026, 12:58 AM UTC

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

  3. identified Feb 16, 2026, 03:21 AM UTC

    The issue has been identified, and we are actively working on remediation.

  4. resolved Feb 16, 2026, 05:18 AM UTC

    We have identified the root cause of the incident and determined that a maintenance activity will be required to fully resolve the issue.

Read the full incident report →

Minor December 17, 2025

[SUPPLY BANK] We are currently experiencing a performance degradation issue on report extraction.

Detected by Pingoru
Dec 17, 2025, 08:43 PM UTC
Resolved
Dec 17, 2025, 09:20 PM UTC
Duration
37m
Affected: REPORT
Timeline · 4 updates
  1. investigating Dec 17, 2025, 08:43 PM UTC

    We are currently investigating this issue.

  2. identified Dec 17, 2025, 08:47 PM UTC

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

  3. monitoring Dec 17, 2025, 09:07 PM UTC

    We have resolved the elevated latency issue during report processing and are actively monitoring the system to ensure stability.

  4. resolved Dec 17, 2025, 09:20 PM UTC

    We have experienced a performance degradation in messaging processing that impacted the timely delivery of messages. As an improvement action, we will optimize the message queue configuration to reduce latency and improve throughput.

Read the full incident report →

Major December 8, 2025

[SUPPLY BANK] We are currently experiencing a performance degradation issue affecting platform.

Detected by Pingoru
Dec 08, 2025, 02:07 PM UTC
Resolved
Dec 08, 2025, 03:27 PM UTC
Duration
1h 20m
Affected: PORTALREPORTNOTIFICATIONWEBHOOKSINTEGRATIONAPIOPERATIONS
Timeline · 6 updates
  1. investigating Dec 08, 2025, 02:07 PM UTC

    We are currently investigating this issue.

  2. identified Dec 08, 2025, 02:22 PM UTC

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

  3. identified Dec 08, 2025, 02:38 PM UTC

    We have identified a communication failure between some of our servers and our workload manager, which affected the application distribution process.

  4. monitoring Dec 08, 2025, 02:59 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Dec 08, 2025, 03:05 PM UTC

    Communication between our services and the workload manager has been restored, and the environment is stable. We continue to monitor the situation and will update this page soon with more information about the incident.

  6. resolved Dec 08, 2025, 03:27 PM UTC

    We have experienced an instability in Kubernetes CoreDNS that caused our internal name resolution to fail, and as a consequence, our alerting pipeline was impacted, since alerts rely on webhooks that could not be delivered. As an improvement action, we will deploy CoreDNS as a DaemonSet to ensure resilience and consistent availability across all nodes. We will also add an internal DNS probe within the cluster to monitor DNS-related failures and provide early detection even when CoreDNS is degraded.

Read the full incident report →