Vendor reports: degradedResolved · vendor status “resolved”Official status API

Service disruption at the Sydney (AU) data center

Reported by Kinsta · Hosting, CDN & Edge · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
Apr 7, 2026, 13:47 UTC
Vendor's clock
Resolved
Apr 7, 2026, 14:20 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
32 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Kinsta reports degraded: "Service disruption at the Sydney (AU) data center".[E1, E2]
  • The vendor marked it resolved at 2026-04-07 14:20 UTC.[E3, E7]

Affected products and regions

  • Components: Sydney, New South Wales, Australia data centers.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-04-07 14:20 UTC · summary s1, evidence 7786e8b28d4f5aae

Evidence (7)
  1. E1Kinsta reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Service disruption at the Sydney (AU) data center". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-04-07 13:47 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Sydney, New South Wales, Australia data centers. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-04-07 14:20 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Sydney, New South Wales, Australia data centers

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Kinsta is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Apr 7, 2026, 13:47 UTCVendor-reported startVendor time
  2. Apr 7, 2026, 14:20 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.