Wyng incident
Some Instagram Content Streams are not collecting content
Wyng experienced a minor incident on September 12, 2023 affecting Instagram Content Stream, lasting 5d 14h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 12, 2023, 11:41 PM UTC
Some Instagram Content Streams are not collecting content. Affected users may see messages about content streams needing to be re-authorized; however attempts to re-authorize may fail. We are investigating this issue.
- identified Sep 13, 2023, 10:18 AM UTC
The root cause is a disruption in Meta Graph API; Meta says: "We’re aware of an issue that may be impacting Graph API me/accounts endpoint. Our engineering teams are actively working to resolve the issue as quickly as possible." This was posted at 3:38 AM EDT. We are monitoring for updates.
- identified Sep 13, 2023, 04:34 PM UTC
Meta continues to actively work on this issue, and is posting status updates here: https://metastatus.com/graph-api. We are monitoring and will post an update when the situation changes.
- identified Sep 14, 2023, 12:33 AM UTC
Meta continues to actively work on resolving this issue. We are monitoring and will post an update when the situation changes.
- identified Sep 14, 2023, 01:28 PM UTC
Most affected Instagram Content Streams have been restored, and are collecting content. However, due to a continued disruption with Meta Graph API, some users may not be able to re-authorize existing streams, or create new streams. We are monitoring for updates.
- identified Sep 15, 2023, 01:09 PM UTC
Most content streams have been restored, and are collecting content. Missed content has been backfilled, with some limitations. While Meta has marked the Graph API disruption resolved, we continue to experience issues getting lists of Instagram accounts from the API. This is preventing some Wyng users from creating or re-authorizing Instagram Content Streams. Many other Graph API users are reporting the same problem. We are monitoring for further updates from Meta, and in parallel, evaluating workarounds.
- monitoring Sep 17, 2023, 03:44 AM UTC
New stream creation and re-authorization of existing streams should now be working for all customers. Meta rolled back the API change that caused the disruption. We are continuing to monitor to verify that the issue is resolved.
- resolved Sep 18, 2023, 02:24 PM UTC
This incident has been resolved.