Is APAC-1: Managed Object Storage down right now?

Partly. As of 2026-10-10 08:11 UTC, APAC-1: Managed Object Storage is having issues, with an open incident: "[SG-SIN1] Managed Object Storage Issue". This page reads the status again every 3 minutes.

Where does this status come from?

From UpCloud's own status page API at https://status.upcloud.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are UpCloud's words. Their page covers more than this page shows; it is narrowed to the parts that concern APAC-1: Managed Object Storage.

Can I get an alert when APAC-1: Managed Object Storage goes down?

Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when UpCloud reports an incident that affects APAC-1: Managed Object Storage and one when it is over. There is also an RSS feed at https://upbutler.com/status/upcloud/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.

How can my agent or app check APAC-1: Managed Object Storage status?

Fetch https://upbutler.com/status/upcloud/apac-1-managed-object-storage/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"upcloud","component":"apac-1-managed-object-storage"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or UpCloud's?

Add "upcloud" to the dependencies of your UpButler workspace. When one of your monitors fails while UpCloud has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is APAC-1: Managed Object Storage down?

APAC-1: Managed Object Storage is having issues

Right now

Partly. [SG-SIN1] Managed Object Storage Issue.

Last checked 28 s ago (2026-10-10 08:11 UTC) from status.upcloud.com · every 180s

For agents

proceed

Proceed, expect slow or flaky responses.

GET upbutler.com/status/upcloud/apac-1-managed-object-storage/status.agent.json

MCP: upstream_status {"service":"upcloud","component":"apac-1-managed-object-storage"}

APAC-1: Managed Object Storage is one of the components UpCloud reports on its status page. European cloud servers and managed databases.

Part of UpCloud status.

What UpCloud says

Degraded· 1 open incident

Taken as is from UpCloud's own status page API. Incident titles and component names below are theirs. Narrowed to what concerns APAC-1: Managed Object Storage.

Open status.upcloud.com

What UpButler measured

There is no keyless endpoint of UpCloud that says anything useful, so UpButler does not probe it. To check your own UpCloud account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at UpCloud for APAC-1: Managed Object Storage

[SG-SIN1] Managed Object Storage Issuemonitoring · impact minor
Since 2026-10-06 06:58 UTC · APAC-1: Managed Object Storage
We have identified the root cause of the service degradation affecting Managed Object Storage in our Singapore (SG-SIN1) data center and have deployed a fix. We currently monitoring the system to ensure long-term stability. Thank you for your patience, and we apologize for any inconvenience caused. If you experience any issues, please contact our support team via live chat or at [email protected].

Text written by UpCloud, shown unchanged.

APAC-1: Managed Object Storage: what UpCloud lists

1 of 1 not operational

SG-SIN1 - Singapore

APAC-1: Managed Object StorageDegraded

APAC-1: Managed Object Storage incidents, last 90 days

2026-07-13: no record
2026-07-14: no record
2026-07-15: no record
2026-07-16: no record
2026-07-17: no record
2026-07-18: no record
2026-07-19: no record
2026-07-20: no record
2026-07-21: no record
2026-07-22: no record
2026-07-23: no record
2026-07-24: no record
2026-07-25: no record
2026-07-26: no record
2026-07-27: no record
2026-07-28: no record
2026-07-29: no record
2026-07-30: no record
2026-07-31: no record
2026-08-01: no record
2026-08-02: no record
2026-08-03: no record
2026-08-04: no record
2026-08-05: no record
2026-08-06: no record
2026-08-07: no record
2026-08-08: no record
2026-08-09: no record
2026-08-10: no record
2026-08-11: no record
2026-08-12: no record
2026-08-13: no record
2026-08-14: no record
2026-08-15: no record
2026-08-16: no record
2026-08-17: no record
2026-08-18: no record
2026-08-19: no record
2026-08-20: no record
2026-08-21: no record
2026-08-22: no record
2026-08-23: no record
2026-08-24: no record
2026-08-25: no record
2026-08-26: no record
2026-08-27: no record
2026-08-28: no record
2026-08-29: no record
2026-08-30: no record
2026-08-31: no record
2026-09-01: no record
2026-09-02: no record
2026-09-03: no record
2026-09-04: no record
2026-09-05: no record
2026-09-06: no record
2026-09-07: no record
2026-09-08: no record
2026-09-09: no record
2026-09-10: no record
2026-09-11: no record
2026-09-12: no record
2026-09-13: no record
2026-09-14: no record
2026-09-15: no record
2026-09-16: no record
2026-09-17: no record
2026-09-18: no record
2026-09-19: no record
2026-09-20: no record
2026-09-21: no record
2026-09-22: no record
2026-09-23: no record
2026-09-24: no record
2026-09-25: no record
2026-09-26: no record
2026-09-27: no record
2026-09-28: no record
2026-09-29: no record
2026-09-30: no record
2026-10-01: no record
2026-10-02: no record
2026-10-03: no record
2026-10-04: no record
2026-10-05: no record
2026-10-06: minor incident
2026-10-07: minor incident
2026-10-08: minor incident
2026-10-09: minor incident
2026-10-10: minor incident

2026-07-135 of 5 days with an incidenttoday

Each bar is a day, coloured by the worst incident UpCloud reported for APAC-1: Managed Object Storage. It is their incident record, not a measurement of uptime.

No finished incidents on record yet since 2026-10-06. UpButler keeps what UpCloud publishes for 90 days from the day it starts tracking a service.

Get alerted when APAC-1: Managed Object Storage goes down

No account. One email when UpCloud reports an incident that affects APAC-1: Managed Object Storage, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add UpCloud as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show APAC-1: Managed Object Storage's current status in a README or an internal wiki. It updates by itself.

[![APAC-1: Managed Object Storage status](https://upbutler.com/status/upcloud/badge.svg?component=apac-1-managed-object-storage)](https://upbutler.com/status/upcloud/apac-1-managed-object-storage)

Tell your outage from UpCloud's

Declare that your project depends on APAC-1: Managed Object Storage. When one of your monitors fails while UpCloud has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - service: upcloud
    components: ["APAC-1: Managed Object Storage"]

Ask before you retry

curl -s https://upbutler.com/status/upcloud/apac-1-managed-object-storage/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "upcloud",
  "component": {
    "slug": "apac-1-managed-object-storage",
    "name": "APAC-1: Managed Object Storage"
  },
  "verdict": "proceed",
  "status": "degraded",
  "reason": "[SG-SIN1] Managed Object Storage Issue",
  "retryAfterSec": null,
  "incident": {
    "title": "[SG-SIN1] Managed Object Storage Issue",
    "url": "https://status.upcloud.com/incidents/zxch4yw7mm87"
  },
  "probe": null
}

Questions

Is APAC-1: Managed Object Storage down right now?: Partly. As of 2026-10-10 08:11 UTC, APAC-1: Managed Object Storage is having issues, with an open incident: "[SG-SIN1] Managed Object Storage Issue". This page reads the status again every 3 minutes.
Where does this status come from?: From UpCloud's own status page API at https://status.upcloud.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are UpCloud's words. Their page covers more than this page shows; it is narrowed to the parts that concern APAC-1: Managed Object Storage.
Can I get an alert when APAC-1: Managed Object Storage goes down?: Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when UpCloud reports an incident that affects APAC-1: Managed Object Storage and one when it is over. There is also an RSS feed at https://upbutler.com/status/upcloud/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check APAC-1: Managed Object Storage status?: Fetch https://upbutler.com/status/upcloud/apac-1-managed-object-storage/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"upcloud","component":"apac-1-managed-object-storage"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or UpCloud's?: Add "upcloud" to the dependencies of your UpButler workspace. When one of your monitors fails while UpCloud has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with UpCloud. Status and incident text belong to UpCloud and are read from their public status source; the probe result is UpButler's own measurement.