We've resolved the error when saving paywalls in the dashboard. Live paywalls were not affected

We've resolved the issue.

From around 10:15 am PDT to 12:00pm PDT we saw elevated error rates on the subscription api, this lead to a degraded purchasing experience for app2web and web2app purchases. This was related to a massive jump in load that unexpectedly caused a cascading failure. We're working to improve the reliability of the internal configuration service to avoid this issue in the future.

We've resolved the issue and are monitoring as the subscriptions-api recovers.

We've resolved the issue but some paywall open data and therefore downstream charts will continue to show less impressions than were actually triggered.

We're investigating an issue with paywall_opens being under-reported.

We've fixed the issue, all data is caught up and performance should be restored

We've monitoring as our systems recover, looking like the presentation delay & stripe checkout should be fixed.

We've identified the issue & are working on a fix

This issue is also causing presentation delays on old SDK versions.

We believe we've resolved the issue and will backfill the missing transaction_complete events.

We've identified the issue & are working on a fix

We're investigating an issue with under-reported stripe transactions

We have resolved the issue and all data is now backfilled.

We've identified the issue & are backfilling

No data is lost but stripe revenue is being under reported

Identified services affected, main service is unaffected. Event processing is delayed

Seeing elevated failure on us-east-1

We've resolved this issue & all users should be able to sign in successfully.

We've identified the issue and are rolling out a fix

We've gotten reports of issues signing in and are investigating

The data is all backfilled now but we're still monitoring to ensure everything is fixed.

We've identified an issue with paywall opens not reporting properly and are now working on a fix. This is only a reporting issue and all paywalls remain operational.

We are seeing increased error rates because of an outage of AWS. We are investigating. Seeing increased paywall fail rate.

We've rolled out a fix and are monitoring the results. We expect any lowered paywall rate to return to normal shortly.

We've identified an issue connecting to S3 from one of our services and have started rolling out a fix

We're investigating a drop in paywall rate for specific SDK versions

We've implemented a fix and we are monitoring the results as we backfill data

We've found the issue and are working on a fix.

We're investigating a delay in processing of App Store Connect events.

The issue causing an error on saving a paywall in the dashboard has been resolved

We are investigating reports of issues with saving paywalls on the Dashboard

We've found the root cause and are backfilling the delayed events to get back up to real time.

We're investigating delayed ingestion of stripe payment data

The issue with saving paywalls has been resolved! Any paywalls that were created by duplicating or from a template during this time will not work, you will need archive them and try again

We've identified an issue with saving changes to paywalls on the dashboard, and are working on a fix!

All data has been backfilled and new events are processing normally

The issue that caused the delay with transactions and revenue data appearing in the dashboard is fixed, and we are monitoring the recovery

We're investigating reports of transactions and revenue data not appearing in the dashboard correctly.

We have no indications at this time that paywalls or the end-user experience is affected

Cloudflare has resolved their issues and Superwall Services are slowly recovering

There was some anomaly in our stream service provider that caused our plan to downgrade leading to a limiting of resources. We’ve resolved the issue and everything should have returned to normal.

While existing paywalls seem unaffected, we're investigating login and dashboard issues reported by some users

Now that AWS has recovered, we have fully resolved the issues we were encountering.

We've identified that most of the issues we're seeing are coming from an inability to provision necessary the instances in AWS to meet demand. This affecting only our events and subscriptions endpoints at this time. Paywall presentation, the dashboard and all other services should be recovered.

We are currently investigating reports of degraded performance and potential service outages. The issue appears to be related to a widespread incident affecting Amazon Web Services (AWS). Our team is actively monitoring the situation and will provide updates as more information becomes available.

We've fixed the issue and backfilled all missing data.

We've noticed that app store connects are delayed and we're working on a fix.

Some webhooks generated in the last 24 hours were not properly delivered to their downstream integrations like Mixpanel, Slack, etc.

We've resolved the issue going forward and will ensure a backfill is completed for all delayed events in the next day.

This issue is now resolved

This has been resolved and all messages have been backfilled

The issue has been resolved, and we are monitoring the process of backfilling data. It will take an estimated ~3 hours to catch up and all events to be processed

We've identified an issue preventing RevenueCat events from being processed correctly in the dashboard, causing new transactions to not appear in the dashboard, and are working on a fix

This is a reporting issue only, no indications of effects on transactions or paywalls

We've resolved the issue and are monitoring the recovery

Currently experiencing degraded perfomance loading paywalls

The issue has been resolved

We've fixed the issue and are working on backfilling the data.

We’ve identified an issue where reporting for some new transactions is not correctly attributing revenue. This affects dashboard reporting only, transactions themselves are processing normally.

Switch your Overview tab to "Paywall Conversions" to see transactions. Dashboard revenue and proceeds may be incorrect until the issue is resolved.

This issue has been resolved

We're investigating a rise in tail latency in our Web Checkout flow

This is now fixed!

Some users seem to observe a crash when trying to duplicate a paywall while we're investigating the issue.

This has been resolved

We've rolled out a fix and are continuing to monitor performance

We've received reports from users about slower than normal dashboard loading times. We're investigating the reported issue.

This is now resolved and the data is backfilled!

We've found the root cause & are working on a fix!

We are investigating reports that new transaction data is not appearing in the Superwall dashboard, will update here as we roll out a fix.

We have no indications that paywalls or payment handling is affected at this time.

The issue upstream seems to be resolved, we'll continue to monitor the situation.

We've identified an ongoing incident in AWS us-east-1 that is impacting our event pipeline https://health.aws.amazon.com/health/status

We're working with our upstream service provider to resolve the issue. There may be some data loss from first-party SDK events (should all retries fail), but all revenue data should be retried by providers automatically.

We're still working with the RC team to backfill the missing data, hopefully will be resolved in the next 24-48 hours.

All new RevenueCat events are correctly forwarding now, and old events during the downtime will be resent and should begin to show tomorrow

We've deployed a fix for an issue that caused some RevenueCat event forwarding to fail and are monitoring recovery

Resolved Third Party issues

There is an ongoing outage of a third party provider, we are investigating impact on our services.

On older SDK versions, we used an API which was still hosted on Heroku. Earlier today, Heroku began a major outage taking down this API completely. We were able to migrate the service over to Cloudflare. Since migrating it, everything is operating as expected.

Heroku is currently experiencing a mayor incident, impacting some Superwall service, we are currently investigating that impact it has on us.

We've resolved the issue and are working on more alerting to automatically scale resources in the future.

We've identified the root cause of the issue, and have scaled up resources to handle increased load. We're monitoring the fix. All systems have seemed to recover.

We've found the root cause of the issues & have implemented fixes.

Our Kafka provider had rate limits which we had recently surpassed causing requests to hang as their system rejected our writes. We've increased the limits and have plans to migrate from a hosted solution to a BYOC solution for more bandwidth and control in the future.

The inability to publish events caused us to loose some data as there were events on device which were never able to be received on the backend. However, for revenue tracking the providers should retry webhooks and data should fill in.

We've identified an issue with our event pipeline timing out for a percentage of requests. We've fixed the issue but are implementing a longer term fix.

We’re seeing intermittent issues where products fail to load or take longer than expected in iOS sandbox environments (including TestFlight and App Review). This appears to be related to delays on Apple’s side and the live production environment is unaffected. We’re actively monitoring and will update as we learn more.