JHB Netflix update:
We have picked up that all our direct Netflix peering sessions are down (from Netflix's end, IPv4 sessions only, v6 are up). We have logged a ticket with Netflix to resolve this. This means that Netflix sees certain prefixes at least 1 AS hop from our network. It seems there is at least one peer at NAP leaking our prefixes onwards to Netflix as well, with insufficient capacity to do so, which is largely why these issues are presenting - However Netflix have no looking glass or insight into what they are learning and where, so it is very difficult to see who this peer is.
We have made some changes and offloaded JHB prefixes to CPT caches, in addition prepended paths to one or two peers we believe may be culprits (and I am seeing an improvement on my netflix stream, but not fast.com), but we do need a response from Netflix's team to diagnose the exact cause. Our teams will continue to try reach out to Netflix for a) our peering sessions and b) to see which peer is leaking our routes.