Y'all can shoot the messenger, or you can thank me for following up and read the "message in a bottle" contained in the article.
I can't make up statements for people, but there's a clue in the article: "One client said that SEACOM told them that it was Property24 that was filtering and blocking traffic from the SEACOM network to their websites."
There's a war going on behind the scenes here, folks.
Unfortunately, SEACOM has declined to provide a detailed technical explanation of what happened for them to decide to de-peer smaller networks. Based on conversations I've had with people in the industry, this is what I've been able to piece together:
- Networks/ASN operators would peer with SEACOM at NAPAfrica, then through some shenanigans would effectively get free transit to other Internet exchange points where SEACOM peers. This was apparently a big problem for transit traffic within Africa.
- SEACOM apparently approached networks who were doing this to negotiate some kind of transit agreement with them, but this never got very far. Apparently the whole free/open peering situation created a loophole that all these (smaller) networks were afraid to have closed, so they wouldn't even meet with SEACOM.
- SEACOM responded by throwing out the bathwater, the baby, and the whole tub. I'm not sure if there is a technical solution that would allow a more nuanced approach instead of just going with the blunt instrument that is selective peering, and unfortunately no-one who knows anything about networking at this level seems to want to talk about the nitty-gritties.