B-feeds is an ingest-layer failover strategy that allows customers to send a second contribution to the same mountpoint on a secondary ingest. In the event of a SharpStream incident on a-feeds, your stream will seamlessly failover to the b-feeds source without losing audience.

If your stream has not reverted to a-feeds after an incident, there are a few reasons this could be: 

Active Maintenance

SharpStream performs regular maintenance to services to ensure service stability. You can find all maintenance announcements on our Announcements page.

Inconsistent B-feeds Setup

Ensure your secondary contribution is identical to your primary contribution. 

If the issue persists, please contact our support team.