Sorry but even on MTN mobile at the time DNS appeared to have failed at the DC and not as a result of routing changes by ISPs. Even their own MTN shop was inaccessible. International services that serve content from hosted CDNs at MTN were inaccessible, like imgur and those using local ns1 DNS like Lifehacker (fastly hosted service) failed when pointing locally. A number of services that relied on ns1 DNS were inaccessible during this time and were not isolated to a single hosting provider internationally, but rather all made use of local DNS nodes that appear to be hosted by MTN. Reports came in of MTN cloud fibre customers having issues THEREAFTER on mybroadband.
All hosted by MTN. So perhaps the DC as a whole was up. But why were these services inaccessible, including MTN's own shop front? And why when bypassing the local node did it work 100%? Why when pointing to the IP did it also fail, indicating that DNS wasn't the root cause but perhaps something else at the DC was giving issues? Are these all unsubstantiated, because we have a trail on our support desk showing otherwise as well as checks on multiple ISPs, DNS services, and MTN's own data network confirming the same experience...