Octopus incident

Deployments using AWS-dependent resources may fail with “No RegionEndpoint or ServiceURL configured.”

Major Resolved View vendor source →
Started
Mar 30, 2026, 12:43 PM UTC
Resolved
Mar 30, 2026, 12:43 PM UTC
Duration
Detected by Pingoru
Mar 30, 2026, 12:43 PM UTC

Affected components

Octopus Cloud

Update timeline

  1. resolved Mar 30, 2026, 12:43 PM UTC

    We have identified the cause of this issue and have produced a fix in Octopus version 2026.2.3825. Please email [email protected] if you are seeing AWS region endpoint errors in your deployments similar to the one in the title and we can discuss upgrade options.

Looking to track Octopus downtime and outages?

Pingoru polls Octopus's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Octopus reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Octopus alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Octopus for free

5 free monitors · No credit card required