EN
Open developer docs
HomeSERVICE STATUS

SERVICE STATUS

Operational context without invented uptime.

Octoryn Router production is operated from Sydney, Australia. This page explains what to inspect and how to report an incident; it does not present static copy as live telemetry.

01SydneyProduction region
02APICustomer request boundary
03No fictionLive state must come from telemetry
01

Production region.

The independent Octoryn Router production stack is located in the AWS Sydney region. Regional placement is part of the operating context, not a guarantee that every upstream provider processes data in the same location.

  • Router production region: Sydney, AustraliaExpand details

    This is part of Production region.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
  • Provider processing location depends on the selected route and policyExpand details

    This is part of Production region.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
  • Use residency policy for workloads with location requirementsExpand details

    This is part of Production region.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
02

Components that affect a request.

A request passes through the public API boundary, Router compute, policy evaluation and an eligible upstream provider. Failures can originate at any of these layers.

  • Public API reachability and authenticationExpand details

    This is part of Components that affect a request.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
  • Router capacity and policy evaluationExpand details

    This is part of Components that affect a request.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
  • Selected provider connectivity and responseExpand details

    This is part of Components that affect a request.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
03

Check status with evidence.

Use a controlled request from the affected environment, then preserve the time, response status and any available correlation metadata. Operator telemetry, logs and infrastructure health determine current service state.

  • Compare from more than one trusted network when reachability is unclearExpand details

    This is part of Check status with evidence.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
  • Do not publish API keys or sensitive request contentExpand details

    This is part of Check status with evidence.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
  • Attach timestamps and sanitized response evidence to escalationExpand details

    This is part of Check status with evidence.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
04

Separate Router and provider incidents.

A provider-specific failure may leave other eligible routes available, while an API-boundary or Router failure can affect multiple providers. Route and policy context helps operators identify the fault domain.

  • Record the requested model or policy aliasExpand details

    This is part of Separate Router and provider incidents.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
  • Note whether failures affect one route or multiple routesExpand details

    This is part of Separate Router and provider incidents.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
  • Use approved fallback policy only when workload requirements permitExpand details

    This is part of Separate Router and provider incidents.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
05

Report what changed.

A useful incident report states the first observed time, affected product or customer environment, route, error category and business impact without disclosing credentials or regulated content.

  • Include timezone with every incident timestampExpand details

    This is part of Report what changed.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
  • Describe frequency and impact, not only one sampleExpand details

    This is part of Report what changed.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls
  • Rotate credentials immediately if exposure is suspectedExpand details

    This is part of Report what changed.. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.

    Explore related controls

OCTORYN ROUTER

Need the wider operating context?

Octopus Core is the operating home for Octoryn and the wider customer platform.

Visit Octopus Core