# Orb: Processing delays

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2025-10-20 07:38 UTC · Resolved: 2025-10-20 23:55 UTC · Duration: 16 h
- Updates: 19 · Affected components: Analytics, API - Analytics, API - Reads, Reads, API - Writes, Writes, Real-time alerting
- [Vendor status page: https://stspg.io/qmzl3vx4ghqc](https://stspg.io/qmzl3vx4ghqc)
- [Company: Orb](https://rewindex.com/company/orb.md)

## Part of an outage event

- [AWS us-east-1 outage, Oct 20, 2025: 141 vendors, 181 incidents](https://rewindex.com/events/2025-10-20-aws-us-east-1)
- This incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +27 min vs AWS’s own post)

```mermaid
flowchart LR
  root["AWS us-east-1<br/>posted 07:11 UTC"]:::root
  before["Posted before AWS did<br/>5 vendors, 4 blamed AWS<br/>Salesforce, Descope, Ashby +2"]:::blames
  root --> before
  h1["Within an hour<br/>18 vendors, 17 blamed AWS<br/>Asana, Firebolt, Monday.com +15"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>30 vendors, 29 blamed AWS<br/>SingleStore, Loops, Buildkite +27"]:::blames
  root --> h4
  later["Later<br/>45 vendors, 44 blamed AWS<br/>RudderStack, Airbyte, Unbounce +42"]:::blames
  root --> later
  p0["Twilio<br/>posted +15 min"]:::blames
  root --> p0
  k0["BigCommerce<br/>+2 h 46 min"]:::hop2
  p0 -->|"blamed Twilio"| k0
  p1["Webflow<br/>posted +4 h 37 min, did not name AWS"]:::timing
  root -.-> p1
  k1["Rootly<br/>+10 h 23 min"]:::hop2
  p1 -->|"blamed Webflow"| k1
  p2["Baseten<br/>posted +4 min"]:::blames
  root --> p2
  k2["Zed<br/>+26 h 20 min"]:::hop2
  p2 -->|"blamed Baseten"| k2
  me["Orb (this incident)<br/>posted +27 min"]:::me
  root -.->|"same window"| me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **investigating** 2025-10-20 07:28 UTC: We are currently investigating API degradation. This seems to be related to an upstream cloud provider outage, and we are closely monitoring.
- **investigating** 2025-10-20 07:38 UTC: We are continuing to see and investigate errors.
- **investigating** 2025-10-20 08:02 UTC: We are continuing to investigate errors.
- **investigating** 2025-10-20 08:17 UTC: We are continuing to investigate this issue. We apologize for the disruption to impacted customers.
- **investigating** 2025-10-20 08:47 UTC: We are continuing to investigate this issue.
- **investigating** 2025-10-20 09:14 UTC: We are continuing to investigate the issue.
- **investigating** 2025-10-20 09:53 UTC: API services are broadly recovered; we're continuing to monitor the situation.
- **investigating** 2025-10-20 10:19 UTC: We are seeing recovery on most API endpoints - some analytics endpoints may still be degraded. We are continuing to work with upstream providers to resolve. Note also that consumption from payment processing may be delayed; we are working through the event backlog here.
- **investigating** 2025-10-20 10:50 UTC: We are failing over affected services gradually for our analytics APIs, which we expect to lead to errors in order to assist with full recovery.
- **identified** 2025-10-20 11:17 UTC: We're continuing to investigate, and working through usage calculation delays.
- **identified** 2025-10-20 11:24 UTC: We are working with our cloud provider to bring on more capacity to help with operational delays.
- **identified** 2025-10-20 11:51 UTC: We are continuing to investigate this issue. We are working with our cloud provider to bring on more capacity to help with operational delays.
- **identified** 2025-10-20 12:43 UTC: We are continuing to work with our cloud provider to bring on more capacity to help with operational delays.
- **identified** 2025-10-20 14:00 UTC: We are continuing to work with our cloud provider to bring on more capacity to help with operational delays. Asynchronous processing may be delayed, including the sending of webhooks.
- **identified** 2025-10-20 14:51 UTC: We are continuing to work with our cloud provider to bring on more capacity to help with operational delays. API calls may not reflect the latest usage data as we work through this.  Asynchronous processing may be delayed, including the sending of webhooks and the receipt of information from your payment gateway connection. We are working diligently on our side to bring these up to date.
- **identified** 2025-10-20 15:51 UTC: We are continuing to work on a fix for this issue.
- **monitoring** 2025-10-20 18:39 UTC: We are seeing significant recovery as capacity is coming back online.
- **monitoring** 2025-10-20 21:03 UTC: Most async processing is operational, including webhooks and receipt of information from your payment gateway connection. We are continuing to monitor remaining recovery of usage calculations and alerting pipelines.
- **resolved** 2025-10-20 23:55 UTC: All systems are operational.


---
Canonical: https://rewindex.com/company/orb/incidents/pv20p6vnl3ng · Markdown: https://rewindex.com/company/orb/incidents/pv20p6vnl3ng.md · JSON: https://rewindex.com/api/v1/companies/orb/incidents/pv20p6vnl3ng · Generated 2026-10-19T23:14:31.230Z