Planned maintenanceResolved · vendor status “resolved”Vendor incident feed · inferred

Maintenance in progress: Scheduled network maintenance in Frankfurt (eu-central-1)

Reported by Checkly · Observability & Incident · source last read 2 min ago

Vendor posted
Nov 3, 2026, 02:00 UTC
When the vendor's feed dated it
Resolved
Nov 3, 2026, 05:00 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
This source does not publish reliable durations

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Checkly reports planned maintenance: "Maintenance in progress: Scheduled network maintenance in Frankfurt (eu-central-1)".[E1, E2]
  • The vendor marked it resolved at 2026-11-03 05:00 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-03 05:00 UTC · summary s1, evidence 433f335c1a5f2c3c

Evidence (7)
  1. E1Checkly reports planned maintenance. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Maintenance in progress: Scheduled network maintenance in Frankfurt (eu-central-1)". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor posted it: 2026-11-03 02:00 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): eu-central-1. (Statuswall) source (opens in a new tab)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-11-03 05:00 UTC. (vendor) source (opens in a new tab)

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

Checkly 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. Nov 3, 2026, 02:00 UTCVendor posted this incidentVendor time
  2. Nov 3, 2026, 05:00 UTCVendor-reported resolutionVendor time

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