CompaniesLaunchDarklyIncidents
LaunchDarkly: [Scheduled] HTTP/2 protocol support and impact on the Erlang SDK
Timeline of updates
- unknown
LaunchDarkly has delayed the service change to enable support for the HTTP/2 protocol for usages from LaunchDarkly's server-side SDKs. This service change will go into effect no earlier than October 2022 after all impacted versions of the Erlang SDK reach their end of life. By this time, all supported SDK versions will be compatible with the proposed service change. As this scheduled maintenance is several months away and as the impact will be limited to then-unsupported SDK versions, we are going to close this scheduled maintenance at this time.
From LaunchDarkly’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.launchdarkly.com (opens in new tab).
Cite this
Maintenance posted by LaunchDarkly, started 2022-03-17 00:11 UTC, not resolved, 1 update(s).
- Title
- [Scheduled] HTTP/2 protocol support and impact on the Erlang SDK
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/6l3drk9dxkmy
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on March 17, 2022LaunchDarkly in March 2022MarkdownJSON