Rewindex

CompaniesDailyIncidents

Daily: Issues connecting to rooms

MinorStatus: resolvedStarted Resolved (6.7 h)5 updatesstspg.io (opens in new tab)
Part of an outage event

AWS outage, Sep 28, 2022 · 16 vendors, 16 incidents

Daily’s incident blames AWS as the cause. (hop 1, posted +0 min vs the first vendor naming AWS)

“…Issues connecting to rooms AWS has resolved their issue, and our operations have returned to normal. AWS has acknowledged an issue with API Gateway in the <tt>us-west-2</tt> region. We're routing API…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour3 vendors, 3 blamed AWSDaily, Unbounce, Gusto1 to 4 hours later3 vendors, 3 blamed AWSLever, Jira, ConfluenceDaily (this incident)posted +0 min
AWSown incident not archivedWithin an hour3 vendors, 3 blamed AWSDaily, Unbounce, Gusto1 to 4 hours later3 vendors, 3 blamed AWSLever, Jira, ConfluenceDaily (this incident)posted +0 min
Daily 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, 3 blamed AWS<br/>Daily, Unbounce, Gusto"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>3 vendors, 3 blamed AWS<br/>Lever, Jira, Confluence"]:::blames
  root --> h4
  me["Daily (this incident)<br/>posted +0 min"]:::me
  h1 --- 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: Core Call Experience

Timeline of updates

  1. investigating

    We're investigating an issue preventing some users from connecting to rooms in the <tt>us-west-2</tt> region.

  2. identified

    We're routing around a possible networking issue to our API gateways in <tt>us-west-2</tt>. This should allow your users to connect to calls, but we're still watching for other networking problems or follow-on effects<a href="https://news.ycombinator.com/item?id=33010341" target="_blank">.</a>

  3. monitoring

    AWS has acknowledged an issue with API Gateway in the <tt>us-west-2</tt> region. We're routing API requests to other regions for now, so everything should be operating normally for you and your users. We'll leave this issue open until AWS has resolved their underlying issue and our health checks return to normal.

  4. monitoring

    We're still watching the ongoing AWS status incident until it's resolved. We'll provide another update if anything changes in the meantime.

  5. resolved

    AWS has resolved their issue, and our operations have returned to normal.

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 stspg.io (opens in new tab).

Daily profileRecent Daily incidentsMarkdownJSON