# Chargebee: AWS DNS Resolver Issue

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2020-07-28 09:00 UTC · Resolved: 2020-07-28 13:15 UTC · Duration: 4.3 h
- Updates: 1
- [Vendor status page: https://status.chargebee.com/incidents/0sxh32cnph80](https://status.chargebee.com/incidents/0sxh32cnph80)
- [Company: Chargebee](https://rewindex.com/company/chargebee.md)

## Part of an outage event

- [AWS outage, Jul 28, 2020: 18 vendors, 18 incidents](https://rewindex.com/events/2020-07-28-aws)
- This incident blames AWS as the cause. (hop 1, posted +30 min vs the first vendor naming AWS)
- Evidence: “…AWS DNS Resolver Issue This incident has been resolved. Jobs that had failed due to this incident have been rescheduled. Based on our logs, very few api calls were affected during the incident.…”

```mermaid
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 3 blamed AWS<br/>Honeycomb, Twilio, Chargebee"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 1 blamed AWS<br/>Stream (GetStream), Elastic Cloud"]:::blames
  root --> h4
  me["Chargebee (this incident)<br/>posted +30 min"]:::me
  h1 --- 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

- **resolved** 2020-07-28 13:15 UTC: This incident has been resolved. Jobs that had failed due to this incident have been rescheduled. Based on our logs, very few api calls were affected during the incident.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/chargebee/incidents/0sxh32cnph80 · Markdown: https://rewindex.com/company/chargebee/incidents/0sxh32cnph80.md · JSON: https://rewindex.com/api/v1/companies/chargebee/incidents/0sxh32cnph80 · Generated 2026-10-19T23:16:10.278Z