Attention community, the Ceramic libp2p pubsub topic is currently experiencing a flood of activity that is overwhelming nodes. This seems to be the same issue we have seen in the past where the same messages get sent around multiple times. We recently restarted the nodes that we (3BoxLabs) operate in an attempt to stem the flood of messages being passed around. It seems to have helped a bit, but not completely resolved the situation. We are continuing to monitor the network and will share any updates to the network status as we have them. Note that we have seen this before and it seems to be an issue with the libp2p gossipsub implementation we build on. We have brought it up to Protocol Labs before and there are some potential improvements to kubo (go-ipfs) on the way that should help, but they haven’t been released yet.
Note that this shouldn’t result in any data loss or corruption to existing data, but could affect the availability of applications built on Ceramic if their Ceramic nodes crash or hang due to being overwhelmed by the volume of pubsub activity