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

Issue provisioning new branches in eu-central-1

Reported by Xata · Databases · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Oct 13, 2026, 11:58 UTC
Vendor's clock
Resolved
Oct 13, 2026, 12:16 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 02:11 UTC
Statuswall's clock
Duration
18 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

  • Xata reports degraded: "Issue provisioning new branches in eu-central-1".[E1, E2]
  • The vendor marked it resolved at 2026-10-13 12:16 UTC.[E3, E7]

Affected products and regions

  • Regions: eu-central-1 (read from the title, so inferred).[E5]

What is unknown

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

Last update in these facts: 2026-11-11 02:11 UTC · summary s1, evidence f4e8003f3cc20cc9

Evidence (8)
  1. E1Xata reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Issue provisioning new branches in eu-central-1". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-10-13 11:58 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): eu-central-1. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-10-13 12:16 UTC. (vendor)
  8. E8First seen by Statuswall: 2026-11-11 02:11 UTC. (Statuswall)

Affected scope

eu-central-1

Components: not stated by the vendor

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

Xata 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. Oct 13, 2026, 11:58 UTCVendor-reported startVendor time
  2. Oct 13, 2026, 12:16 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:11 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall