rewindex

CompaniesStatuspageIncidents

Statuspage: Elevated Server Errors on Public Pages

No impact listedStatus: resolvedStarted Resolved (30 min)3 updatesmstspg.co (opens in new tab)
Part of an outage event

AWS outage, Sep 18, 2023 · 18 vendors, 18 incidents

Statuspage’s incident started in the same window without naming AWS (timing only, not evidence of a link). (hop 1, posted +43 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

depends on AWSAWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSDagster, Snowflake, Vanta1 to 4 hours later7 vendors, 5 blamed AWSAmplitude, Temporal Cloud, Coralogix, Confluent +3Known dependency5 vendorsBandwidth, Segment, Jira, Daily +1Statuspage (this incident)posted +43 min
depends on AWSAWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSDagster, Snowflake, Vanta1 to 4 hours later7 vendors, 5 blamed AWSAmplitude, Temporal Cloud,Coralogix, Confluent +3Known dependency5 vendorsBandwidth, Segment, Jira, Daily+1Statuspage (this incident)posted +43 min
Statuspage is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 1 blamed AWS<br/>Dagster, Snowflake, Vanta"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>7 vendors, 5 blamed AWS<br/>Amplitude, Temporal Cloud, Coralogix, Confluent +3"]:::blames
  root --> h4
  dr["Known dependency<br/>5 vendors<br/>Bandwidth, Segment, Jira, Daily +1"]:::hop2
  root -.->|"depends on AWS"| dr
  me["Statuspage (this incident)<br/>posted +43 min"]:::me
  root -.- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Hosted Pages - Status Embed WidgetStatus Embed WidgetHosted Pages - HTTPS PagesHTTPS PagesHosted Pages - HTTP PagesHTTP Pages

Timeline of updates

  1. investigating

    We are investigating cases of degraded performance for public pages. Pages may be failing to load or loading more slowly than normal.

  2. monitoring

    We have identified the issue and a fix has been implemented. We have scaled our services to mitigate the issue and are monitoring the results.

  3. resolved

    This incident has been resolved.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on mstspg.co (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Statuspage, started 2023-09-18 18:50 UTC, resolved after 30 min, 3 update(s).

Title
Elevated Server Errors on Public Pages
Vendor
Statuspage
Date
URL
https://rewindex.com/company/statuspage/incidents/vk7b8qt8kctm

Statuspage profileRecent Statuspage incidentsAll outages on September 18, 2023Statuspage in September 2023MarkdownJSON